Git access
AI Developer connects to your repository over HTTPS. This applies to all three apps. Self-hosted GitHub, GitLab and Bitbucket instances work as well.
- Open Project / Space Settings → Apps and select the AI Developer app.
- Enter the HTTPS repository URL, e.g.
https://github.com/your-org/repo.git. - Enter the base branch to start from, e.g.
main. - Enter your Git username and the access token as the password (see below).
- Optionally set an identifier to tell multiple repositories apart.
You can configure more than one repository per project. In the issue panel a repository selector then lets you choose where the work goes. Use the identifier to give each repository a recognizable name.
Access tokens
Give the token only the access it needs: read and write on the repository contents, plus pull or merge requests if you want those created.
Use a Personal Access Token. Fine-grained tokens are recommended for the tightest control.
- Go to Settings → Developer settings → Personal access tokens → Fine-grained tokens.
- Click Generate new token, give it a name and set an expiry date.
- Under Repository access, select only the repositories AI Developer should work on.
- Set permissions: Contents read & write · Commit statuses read & write · Pull requests read & write (if you want PRs created).
- Generate the token, copy it and paste it as the password in the Jira settings.
Use a Personal Access Token or a Project Access Token (scoped to a single repository).
- User token: Profile → Preferences → Access Tokens. Project token: Project → Settings → Access Tokens.
- Give it a name, an optional expiry and the scopes
read_repositoryandwrite_repository(addapiif merge request creation is needed). - Create the token, copy it and paste it as the password in the Jira settings.
Use an App Password (or API token on newer Bitbucket instances).
- Go to your avatar → Personal settings → Access management → App passwords.
- Click Create app password, give it a label and select the scopes Repository read & write · Pull requests read (and write if you want PRs).
- Create the token, copy it and paste it as the password in the Jira settings.
Branches
The AI never pushes to your base branch. Results are committed to a new branch named ai/<ISSUE-KEY>-<random>, for example ai/PROJ-123-a1b2c3. Follow-up changes, such as a comment mention or Change spec, continue on the same branch. Review and merge it the way you do for any other branch.
Support
For help or to report issues, email support@smart-fusion.tech.