Git Integration

Storing your BlinqIO project in a private Git repository gives you full version control, collaborative workflows, and a single source of truth for your test code. Once connected, changes sync automatically in both directions: edits you make in BlinqIO appear in Git, and commits you push to Git appear in BlinqIO.

Who can configure Git integration

Only the project owner (the admin who created the project) can set up or edit the Git integration. Collaborators and invited users cannot configure it.

Setting up Git integration

1. Open your account and go to Settings > Integrations.
2. Click Set up Git.
3. Enter your private Git repository URL.
4. Enter your Git username.
5. Generate an access token from your Git provider (see token generation tips below).
6. Click Authorize to complete the integration.

Supported providers and URL formats

Provider	URL format
GitHub	https://github.com/YourUsername/YourRepo.git
Bitbucket	https://bitbucket.org/workspace-id/repo-name.git
GitLab	https://gitlab.com/username/repo-name.git

Editing the integration

To update your Git credentials (for example, when a team member leaves):

1. Go to Settings > Integrations.
2. Click Edit configuration.
3. Update the repository URL, username, or access token as needed.

Sync behavior

Once integration is active, changes flow in both directions automatically:

• Edits in BlinqIO (recording, generating, or modifying scenarios) commit to the connected branch.
• Commits pushed to the repository reflect back in BlinqIO.

Branching

You can switch branches or create new ones directly from the BlinqIO interface:

1. Open your Git-integrated project.
2. Use the Branch selector in the top bar (next to the Project and Environment selectors).
3. From the dropdown you can:
   • Create a new branch: select a source branch, enter the new branch name, and confirm.
   • Switch to an existing branch: select it from the list.

All changes made through the project interface apply only to the currently selected branch. The last selected branch is remembered and reopened by default.

Merging

BlinqIO does not handle pull requests. When you are ready to merge:

1. Go to your Git provider (GitHub, GitLab, or Bitbucket).
2. Open a pull request from your working branch into the target branch.
3. Review, approve, and merge as you normally would.

Migration notes

Migrating a BlinqIO project to a private Git repository is one-way and cannot be reversed. Before migrating, ensure:

• The default branch of your Git repository is named main. Other default branch names are not currently supported.
• You have a valid repository URL, username, and access token ready.

For detailed migration steps per provider, see the migration instructions.

Generating access tokens

Each Git provider has its own process for creating access tokens. Here is a summary:

GitHub

1. Go to Settings > Developer settings > Personal access tokens (classic).
2. Click Generate new token (classic).
3. Set expiration to No expiration.
4. Under scopes, select repo for full repository access.
5. Click Generate token and save it securely.

If the repository belongs to an organization with SSO enabled, authorize SSO for the token under Settings > Developer settings > Personal access tokens (classic) by clicking Configure SSO next to the token.

Bitbucket

1. Go to Personal Bitbucket settings > Access Management > App passwords.
2. Click Create app password.
3. Set a label and select these permissions: Repository (Read & Write), Pull requests (Read & Write).
4. Click Create and save the password securely.

GitLab

1. Go to Settings > Access tokens.
2. Click Add new token.
3. Enter a token name and set expiration to one year.
4. Set the role to Owner.
5. Select the read_repository and write_repository scopes.
6. Click Create personal access token and save it securely.

WARNING

All providers show the token only once. Save it immediately: you cannot retrieve it after leaving the page.