Setting Up Git Credentials

Ileen needs write access to your Git repositories to push code. This guide covers how to create and configure a Personal Access Token (PAT) for the most common Git hosts.

Applies to: Design Mode (Developer Setup) · Develop Mode (Project Setup)

---

Required permissions

Ileen only needs the permissions to read and write repository content. It does not need organisation admin, CI/CD, or webhook permissions.

Git host	Token scope
GitHub	repo (full repository access)
GitLab	read_repository + write_repository
Bitbucket	Repository: Read + Write
Other hosts	Read + write on the target repository

---

GitHub — create a PAT

1. Go to GitHub → Settings → Developer settings → Personal access tokens → Tokens (classic).
2. Click Generate new token (classic).
3. Set an expiry (90 days is a good balance; you can regenerate later).
4. Under Select scopes, tick only repo.
5. Click Generate token and copy the token 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 — create a PAT

1. Go to GitLab → User settings → Access tokens.
2. Click Add new token.
3. Give it a name (e.g. Ileen), set an expiry.
4. Under Select scopes, tick read_repository and write_repository.
5. Click Create personal access token and copy the value.

---

Bitbucket — create an App Password

Bitbucket uses App Passwords instead of PATs.

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

When entering credentials in Ileen, use your Bitbucket username as the username and the App Password as the token.

---

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: If all your repositories are on the same Git host and account, enable “Share this token across all repositories” — 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 a single existing repository:

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 Connect & Analyse.

---

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 Git host’s 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)

---

Next steps

• Tutorial 01: Design Mode — full walkthrough including Git setup
• Tutorial 02: Develop Mode — connecting an existing repository