Git Repository Configuration

Overview

Agiloop IMPLEMENT uses your Git repository as the source of truth for all generated application code.

Before IMPLEMENT can generate or manage feature code, you must configure access to a Git repository created specifically for your project.

Repository configuration is managed from your Agiloop project settings.

Supported Git Providers

Agiloop IMPLEMENT supports multiple Git hosting platforms, including:

• GitHub
• GitLab
• Bitbucket
• Azure DevOps

Additional providers may be supported in future releases.

How IMPLEMENT Uses Your Repository

IMPLEMENT follows a branch-based workflow for feature generation and review.

When IMPLEMENT begins processing a feature, it:

1. Creates a dedicated feature branch
2. Performs code generation
3. Runs validation and verification processes
4. Commits generated changes to the feature branch
5. Moves the feature into the Review status
6. Creates a Pull Request (PR) or Merge Request (MR) into the configured code branch

This workflow allows generated code to be reviewed, validated, and approved before merging into your primary development branch.

Feature Approval and Merge Workflow

Once a feature has been reviewed and approved:

• IMPLEMENT performs the merge process
• The feature branch is merged into the configured code branch
• The feature moves into the Done status

This creates a complete implementation lifecycle from specification through generated code delivery.

Repository Permissions

The API token or access credentials configured in your project settings must have sufficient permissions to perform repository operations.

Depending on your Git provider, IMPLEMENT may require permission to:

• Read repository contents
• Create branches
• Commit changes
• Create Pull Requests or Merge Requests
• Approve or update PR/MR metadata
• Merge branches

Some providers require explicit merge permissions in addition to PR creation permissions.

If permissions are incomplete, IMPLEMENT may fail during branch creation, PR generation, or merge operations.

How to Configure Your Repository

Step 1: Create Your Repository

Create a Git repository for your project using your preferred provider.

Step 2: Open Project Settings

In Agiloop, navigate to your project settings.

Step 3: Configure Repository Access

Provide the required repository details, including:

• Git provider
• Repository URL or identifier
• Authentication credentials or API token
• Default code branch
• Optional provider-specific settings

Step 4: Verify Permissions

Ensure the configured credentials have sufficient access to:

• Create branches
• Push commits
• Create PRs/MRs
• Merge approved changes

Recommended Workflow

Agiloop recommends using a dedicated integration branch such as:

• develop
• main
• integration
• staging

IMPLEMENT will target this configured branch when generating Pull Requests or Merge Requests.

Best Practices

• Use repositories dedicated to a single Agiloop project
• Create least-privilege API tokens while still allowing merge operations
• Protect production branches using your provider’s branch protection rules
• Require human review for sensitive or production-critical features
• Regularly rotate repository credentials and access tokens

Example Workflow

1. Feature enters implementation
2. IMPLEMENT creates feature/F-102-user-auth
3. Code is generated and validated
4. Changes are committed to the feature branch
5. PR/MR is created into develop
6. Reviewer approves the feature
7. IMPLEMENT merges the branch into develop
8. Feature moves to Done