Setting Up Git Credentials

Ileen needs write access to your Git repositories to push code and manage pull requests (or merge requests). This guide covers how to create and configure a Personal Access Token (PAT) for each supported provider.

Applies to: Design Mode (Developer Setup) · Develop Mode (Project Setup) · Deploy Mode (fix-and-redeploy)

---

Supported providers

Ileen supports GitHub, GitLab, Bitbucket Cloud, and Azure DevOps. The provider is detected automatically from your repository URL — no manual selection needed.

Provider	Clone URL format	PAT guide
GitHub	https://github.com/owner/repo.git	GitHub PAT
GitLab	https://gitlab.com/owner/repo.git	GitLab PAT
Bitbucket	https://bitbucket.org/owner/repo.git	Bitbucket PAT
Azure DevOps	https://dev.azure.com/org/project/_git/repo.git	Azure DevOps PAT

⚠️ GitLab nested groups are not supported. Ileen requires repositories to be at the root level of a GitLab group (e.g. https://gitlab.com/your-group/your-repo). Repositories inside nested subgroups (e.g. https://gitlab.com/your-group/subgroup/repo) will not work correctly — the automated merge request workflow cannot complete, and the development pipeline will fail.

---

GitHub

Required permissions

Permission	Access
Metadata	Read
Contents (code)	Read and Write
Commit statuses	Read and Write
Merge queues	Read and Write
Pull requests	Read and Write

Create a fine-grained PAT

GitHub’s fine-grained personal access tokens let you grant exactly the permissions above, scoped to specific repositories.

1. Go to GitHub → Settings → Developer settings → Personal access tokens → Fine-grained tokens.
2. Click Generate new token.
3. Give it a name (e.g. Ileen) and set an expiry (90 days is a reasonable default).
4. Under Repository access, select Only select repositories and choose the repos you’ll connect to Ileen.
5. Under Repository permissions, set:
   • Contents → Read and Write
   • Commit statuses → Read and Write
   • Merge queues → Read and Write
   • Pull requests → Read and Write
   • Metadata is set to Read automatically.
6. Click Generate token and copy it immediately — it won’t be shown again.

Tip

If your organisation uses SSO (SAML), you must also authorise the token for your organisation: click Configure SSO next to the token after creating it.

---

GitLab

Required permissions

Permission	Access
api (read and write)	Required

GitLab uses a single broad api scope for personal access tokens.

Create a PAT

1. Go to GitLab → User Settings → Access Tokens.
2. Give it a name (e.g. Ileen).
3. Under Select scopes, check api.
4. Set an expiry date (optional but recommended).
5. Click Create personal access token and copy it immediately.

Note

Self-hosted GitLab instances are also supported. Just paste your repository URL — no extra configuration is needed.

---

Bitbucket Cloud

Required permissions

Permission	Access
Repositories	Read and Write
Pull requests	Read and Write

Create an App Password

Bitbucket uses App Passwords for repository-level access:

1. Go to Bitbucket → Personal settings → App passwords.
2. Click Create app password.
3. Give it a label (e.g. Ileen).
4. Under Permissions, select:
   • Repositories → Read and Write
   • Pull requests → Read and Write
5. Click Create and copy the password immediately.

Note

Bitbucket Workspace Access Tokens with repository and pull request scopes are also supported.

---

Azure DevOps

Required permissions

Permission	Access
Code	Read & Write
Pull Request Threads	Read & Write

Create a PAT

1. Go to Azure DevOps → User settings → Personal access tokens.
2. Click New Token.
3. Give it a name (e.g. Ileen).
4. Under Scopes, select Custom defined and enable:
   • Code → Read & write
   • Pull Request Threads → Read & write
5. Set an expiration (up to 1 year).
6. Click Create and copy the token immediately.

---

Entering credentials in Ileen

Design Mode — Developer Setup

When you reach Stage 4 (Development) in Design Mode, the Developer Setup screen lists every repository defined by the Tech Leader. For each one:

1. Enter the repository HTTPS URL (e.g. https://github.com/acme/ecommerce-api).
2. Enter the Personal Access Token.
3. Choose the base branch (defaults to main).

Shared token: When the project has more than one repository, the Developer Setup screen shows a “Shared Access Token (optional)” field at the top. Enter your PAT there and it will be used for every repo that doesn’t have its own token below — you only need to enter it once.

Caution

Repositories must be empty before Ileen connects to them. Ileen pushes the initial commit, folder structure, and boilerplate. If the repository already has content, the push will fail.

Develop Mode — Project Setup

Develop Mode connects to one or more existing repositories:

1. Enter the repository URL.
2. Choose the base branch (the branch Ileen will read and commit to).
3. Enter the PAT if the repository is private.
4. Click Create Project.

Deploy Mode — fix-and-redeploy commits

Deploy Mode also uses your Git PAT when the Deploy Agent applies code fixes during a fix-and-redeploy cycle. When a deployment fails and the agent repairs the code, it commits the change and pushes it to the configured branch before triggering a new build.

No extra configuration is needed — the same PAT you entered in Developer Setup is reused automatically. Make sure it has Contents: Read and Write permission on every repository in the project (see the Required permissions table above).

---

Customizing Git commit identity

By default, all commits pushed by Ileen use the identity Ileen (ileen@hypaz.com) as the author and committer. You can override this on your Account page to have commits appear under your own name and email address instead.

How to set your own identity

1. Open the user menu (top-right avatar) and click Account.
2. Scroll to the Git Commit Identity section.
3. Fill in the Git author name and Git author email fields with your preferred identity.
4. Click Save to apply the change.

Note

Only commits created after you save your identity are affected. Previous commits retain their original author — Ileen does not rewrite Git history.

If you leave either field empty, Ileen falls back to the default identity for that field. For example, setting only the name will use Your Name (ileen@hypaz.com) on future commits.

---

Token security

• Tokens are encrypted at rest and in transit.
• They are used only during active coding jobs and deployment runs.
• Tokens are never included in logs or error messages.
• Revoke a token at any time from your provider’s token settings without affecting other Ileen functionality.

---

Troubleshooting

Error	Likely cause	Fix
Authentication failed	Wrong token or expired	Regenerate the token and update it in Ileen
Repository not found	URL typo or PAT has no access to the repo	Check the URL and token scopes
Push rejected: non-empty repository	Repo already has content	Create a new empty repository
SSO required	GitHub SAML org requires SSO authorisation	Authorise the token for the org (see GitHub tip above)
Merge request not created	GitLab nested group	Use a repository at the root level of a GitLab group

---

Next steps

• Creating a repository — step-by-step for each provider
• Tutorial 01: Design Mode — full walkthrough including Git setup
• Tutorial 02: Develop Mode — connecting an existing repository