Skip to content

Add CI instructions for GitLab #772

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 14, 2025
Merged

Add CI instructions for GitLab #772

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions General-Microproject-Information.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,26 +110,27 @@ the following steps:
document.

* *Optional, but recommended:*
With an account at GitHub, you can use GitHub CI to test your changes

With an account at GitHub or GitLab, you can use the CI to test your changes
on Linux, Mac and Windows. See
[examples](https://github.com/git/git/actions/workflows/main.yml)
of recent CI runs.
[GitHub exmamples](https://github.com/git/git/actions/workflows/main.yml), [GitLab examples](https://gitlab.com/git-scm/git/-/pipelines) of recent CI runs.

To run these tests against your own branch,
[create a fork](https://help.github.com/articles/fork-a-repo/)
of [Git](https://github.com/git/git) on GitHub and switch to it. At the
To run these tests against your own branch:
* **GitHub**: [create a fork](https://help.github.com/articles/fork-a-repo/) of [Git](https://github.com/git/git) on GitHub and switch to it. At the
top bar select [Actions tab](https://github.com/git/git/actions)
and perform the initial setup to enable it for your fork. After enabling it,
CI will run for a specific branch of your fork whenever you push new changes
to it in GitHub. You can monitor the test state of all your branches in the
same [Actions tab](https://github.com/git/git/actions) of your fork.
* **GitLab**: [create a fork](https://docs.gitlab.com/user/project/repository/forking_workflow/#create-a-fork) of [Git](https://gitlab.com/git-scm/git) on GitLab and switch to it. CI will run for a specific branch of your fork whenever you push new changes
to it in GitHub. You can monitor the test state of all your branches in the [Build > Pipeline](https://gitlab.com/git-scm/git/-/pipelines) section of your fork.

If a branch did not pass all test cases then it is marked with a red cross. In
that case you can click on the failing job and navigate to
`ci/run-build-and-tests.sh` and/or \
`ci/print-test-failures.sh`. You can also
download "Artifacts" which are tarred (or zipped) archives with test data
relevant for debugging. Fix the problem and push your fix to your GitHub fork.
relevant for debugging. Fix the problem and push your fix to your fork.
This will trigger a new CI build. Ensure all tests pass.

* Submit your change to the Git mailing list. For this step you
Expand Down