Note: GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap.
Anyone with write permission to a repository can set up continuous integration (CI) using GitHub Actions.
After you set up CI, you can customize the workflow to meet your needs.
- On GitHub Enterprise Server, navigate to the main page of the repository.
- Under your repository name, click Actions.
- Find the template that matches the language and tooling you want to use, then click Set up this workflow.
- Click Start commit.
- At the bottom of the page, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. For more information, see "Creating a commit with multiple co-authors."
- Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is the default branch, you should choose to create a new branch for your commit and then create a pull request. For more information, see "Creating a new pull request."
- Click Propose new file.
Once a push is made to your repository, you can follow the status and detailed logs of your continuous integration workflow run on GitHub and receive customized notifications. For more information, see "Configuring notifications" and "Managing a workflow run."
A status badge shows whether a workflow is currently failing or passing. A common place to add a status badge is in the
README.md file of your repository, but you can add it to any web page you'd like. By default, badges display the status of your default branch. You can also display the status of a workflow run for a specific branch or event using the
event query parameters in the URL.
For more information, see "Adding a workflow status badge."