Skip to content

Latest commit

 

History

History
43 lines (32 loc) · 1.8 KB

README.md

File metadata and controls

43 lines (32 loc) · 1.8 KB

Add overlays for your pull requests in this directory

When your pull request breaks an external project we test in our CI and you have prepared a branch with the fix, you can add an "overlay" to your pull request to test it with the adapted version of the external project.

An overlay is a file which defines where to look for the patched version so that testing is possible. It redefines some variables from ci-basic-overlay.sh: give the name of your branch / commit using a _CI_REF variable and the location of your fork using a _CI_GITURL variable. The _CI_GITURL variable should be the URL of the repository without a trailing .git. If the fork is not on the same platform (e.g. GitHub instead of GitLab), it is necessary to redefine the _CI_ARCHIVEURL variable as well.

Moreover, the file contains very simple logic to test the pull request number or branch name and apply it only in this case.

The name of your overlay file should start with a five-digit pull request number, followed by a dash, anything (for instance your GitHub nickname and the branch name), then a .sh extension ([0-9]{5}-[a-zA-Z0-9-_]+.sh).

Example: 10185-SkySkimmer-instance-no-bang.sh containing

if [ "$CI_PULL_REQUEST" = "10185" ] || [ "$CI_BRANCH" = "instance-no-bang" ]; then

    quickchick_CI_REF=instance-no-bang
    quickchick_CI_GITURL=https://github.com/SkySkimmer/QuickChick

fi

(CI_PULL_REQUEST and CI_BRANCH are set in ci-common.sh)

Branching conventions

We suggest you use the convention of identical branch names for the Coq branch and the CI project branch used in the overlay. For example, if your Coq PR is coming from the branch more_efficient_tc, and that breaks ltac2, we suggest you create a ltac2 overlay with a branch named more_efficient_tc.