Native Git Repository
APIGit is built entirely on native Git, so every commit, branch, tag, pull request, and rebase works exactly as you expect. Store your API specs, mock-server scripts, test cases, and Markdown docs in a single repo and manage them with the full power of Git. Need external sync? Hook APIGit to GitHub, GitLab, Bitbucket, or any self-hosted server for effortless one- or two-way mirroring and friction-free team collaboration.
Everything saved in Git repository
In APIGit, your OpenAPI specifications, API design, mock server codes, and markdown documents are all stored in Git repositories within APIGit.
- Change Tracking & Recovery
- API Evolution Visibility
Multiple branches or tags
Making branches and tags are efficient ways to organize your API designs and maintain multiple versions of your API.
In addition, adding feature branches allows for API modification made to the API repository. When a developer starts working on a new task or feature, they can create a branch from the main branch. The primary branch always looks stable and production-ready.
- Branch-Based Development
- Version Organization
Commit history
Git history of commit makes it easy for you to review the commit history, view the differences of commits, and understand the context of files in the point of commit.
This allows your team to track changes over time, understand why decisions were made, and revert to previous versions if needed.
- Commit History Tracking
- Change Context Understanding
Push mirrors to sync repositories
By configuring push mirrors, you can synchronize your APIGit repositories with any external git server such as GitHub, GitLab, Bitbucket, or your own git server within your organization. This allows you to maintain a single source of truth while still leveraging external tools and workflows.
Push mirrors ensure that changes made in APIGit are automatically reflected in your external repositories, keeping everything in sync.
- Push Mirror Synchronization
- Cross-Repository Consistency
Webhook to monitor activities
By configuring webhooks, you can automatically receive notifications when specific events occur, such as pushing, merging, committing, and more. This allows you to integrate with other systems and take action when necessary.
Webhooks can trigger CI/CD pipelines, notify team members, update documentation, or perform any other automated tasks when changes are made to your API.
- Webhook Integration
- Event-Triggered Actions
Pull request between branches
Using pull requests is a common method for merging changes between branches, particularly from a feature branch to a production branch. This process not only provides a clear and organized git history, but also enables a review and approval process for production.
By implementing pull requests, you can ensure higher code quality and improve your overall development process. Team members can review changes, suggest improvements, and approve modifications before they are merged into the main codebase.
- Pull Request Workflow
- Collaborative Change Review
Discussion and review under a pull request
With each pull request, you have the ability to review all the details of the related commits, including the changed files, and provide comments or engage in discussions about the changes as necessary.
This allows for thorough review and collaboration before merging the changes to the production branch. Team members can discuss implementation details, suggest improvements, and ensure that all changes meet quality standards and project requirements.
- Detailed Change Examination
- Pre-Merge Collaboration
Benefits of Native Git Support
APIGit's native Git support provides numerous advantages for API development teams
Unified Repository
Store all your API artifacts—specifications, mock servers, documentation, and tests—in a single Git repository with complete version control.
Branching & Tagging
Organize API versions with branches and tags, allowing teams to work on features in parallel while maintaining stable production versions.
Change History
Track every change with detailed commit history, making it easy to understand context, review differences, and revert to previous versions when needed.
External Integration
Synchronize with GitHub, GitLab, Bitbucket, or your own Git server using push mirrors, maintaining a single source of truth across all platforms.
Workflow Automation
Configure webhooks to trigger CI/CD pipelines, notify team members, and automate tasks when changes occur in your API repository.
Code Review
Implement pull requests with detailed discussions and reviews, ensuring all API changes meet quality standards before merging to production.
Ready to streamline your API development with Git?
Experience the power of native Git integration with APIGit and transform how your team collaborates on API development.