You will need roughly 2 minutes to read this article.
Integration between a repository and any forked repositories is not currently supported for any SCM. You can setup forked repositories as separate projects on Codeship, but any builds for the forked repository will not link back to the parent repository.
Codeship can clone your GitHub repositories and report build statuses back via the GitHub API.
Required GitHub permissions.
Codeship can clone your Bitbucket repositories and report build statuses back via the Bitbucket API.
Required Bitbucket permissions.
In addition to Git repositories, Mercurial repositories on Bitbucket are also supported.
Codeship can clone your GitLab repositories and report build statuses back via the GitLab API.
Required GitLab permissions.
There is support of GitHub Enterprise, GitLab Community Edition, GitLab Enterprise Edition and Bitbucket Server products.
You can read the self-hosted Git documentation to learn more.
If you use self-hosted git servers, we have an IP Whitelisting option, which allows you to provide access to your git server, from just eight specific IP addresses. See IP Whitelisting documentation for more details.
If you want to see which services you’re connected to, or perhaps ensure your username is registered so your builds show up on the personal dashboard, you can go to your Connected Services page. This allows you to add more connections or update/disable your existing connections.
Note: Before disconnecting a service, you should check to see if it’s being used by a project to communicate with your git server. The account used to connect to the git server is shown on the project’s
General settings (Project -> Project Settings -> General)
We are continually evaluating our SCM integration support. If there is something you would like to see, please get in touch and let us know more details about your SCM needs.
Do you think we need to improve this article? If so, please submit our feedback form to help us improve this article!