DIJJI.ai Academy

Getting Started

Create your first project

A project is where DIJJI.ai does its work. It points at one GitHub repository, belongs to one team, and holds the pipeline and the tasks that run against that repository. This page walks through creating one.

For how projects relate to tasks and runs, see Projects, tasks, and runs. This page is the hands-on setup.

Before you start

Two things need to be in place first:

  • A connected GitHub account. A project points at a repository, so DIJJI.ai needs GitHub access before you can create one. If you haven’t done this yet, see Connect GitHub. Open the New Project form without a GitHub account connected and DIJJI.ai shows a notice and keeps the New Project button disabled.
  • At least $100 in your balance. Creating a project requires a minimum balance of $100.00. This is higher than the $10.00 it takes to start a task — it reserves room for the work the project will do. If your balance is short, DIJJI.ai blocks the creation and tells you the current balance and what’s required. Your organization’s balance lives on the Usage screen (the Usage icon on the left rail), under its Organization scope; topping it up is admin-only, so if you’re a member you’ll see a note asking an admin to manage credits. For what a balance is and how charges work, see Credits and billing.

Open the New Project form

Select Projects — the second icon down the left rail — then select New Project in the top-right corner. You can also open the form straight away with the New project action in the command palette (Cmd-K). If you have no projects yet, the empty state on the Projects page offers the same New Project button.

The form is grouped into three cards: Project Details, Team & Repository, and Configuration.

Fill in the project details

  • Project Name (required) — how the project appears across DIJJI.ai. Use something short and recognizable, for example Checkout Service. It must be between 2 and 128 characters.
  • Description (optional) — a short line on what the project is for, up to 1024 characters.

Choose the team and repository

  • Team (required) — which team the project belongs to. If your organization has only the General team, it’s selected for you. Otherwise, pick from the dropdown.
  • GitHub Integration (required) — which connected GitHub account the repository comes from. If you’ve connected only one account, it’s selected for you; if you’ve connected more than one, choose the right one here.
  • Repository (required) — the repository this project works on. The dropdown lists every repository the selected GitHub account has shared with DIJJI.ai, with private ones marked (private). To widen the list, share more repositories on GitHub — see Connect GitHub.
  • Trunk Branch (optional) — the long-lived branch that feature branches are created from. When you pick a repository, this fills in with that repository’s default branch. Leave it as-is unless your repository uses a different trunk — for example a legacy master branch, or a GitFlow setup where the trunk differs from the final pipeline stage.

Changing the GitHub account clears the repository and trunk branch, so set the account first, then the repository.

Choose your PM tool

Under Configuration, the PM Tool setting decides where your tasks come from. The default, GitHub Issues, reads issues from the repository you just chose and turns them into tasks. It’s the simplest path and the right pick if your team plans work in GitHub.

If your team plans work in Jira instead, pick Jira — the form then asks for a Jira Account and a Jira Project from the synced list, and tasks will come from dijji-labeled issues in that project. Jira appears here only when an admin has connected Jira on the Integrations page; see Connect Jira if it isn’t connected yet. The PM tool is chosen at creation and stays with the project.

Create the project

Select New Project at the bottom of the form. If anything is missing or invalid, DIJJI.ai marks the field with an inline message — fix it and submit again.

When the project is created, DIJJI.ai takes you straight to the project’s Overview page.

What’s next

Your project exists, but it has no pipeline yet — the path your work travels before it lands. The next step is to design that pipeline: add a stage, pick its branch, and decide whether it waits for your review before advancing — see Design your first pipeline.