mirror of
https://github.com/git/git
synced 2024-08-27 03:29:21 +00:00
21c82dcd62
When we added config to skip CI for certain branches in e76eec3554 (ci:
allow per-branch config for GitHub Actions, 2020-05-07), there wasn't
any way to avoid spinning up a VM just to check the config. From the
developer's perspective this isn't too bad, as the "skipped" branches
complete successfully after running the config job (the workflow result
is "success" instead of "skipped", but that is a minor lie).
But we are still wasting time and GitHub's CPU to spin up a VM just to
check the result of a short shell script. At the time there wasn't any
way to avoid this. But they've since introduced repo-level variables
that should let us do the same thing:
https://github.blog/2023-01-10-introducing-required-workflows-and-configuration-variables-to-github-actions/#configuration-variables
This is more efficient, and as a bonus is probably less confusing to
configure (the existing system requires sticking your config on a magic
ref).
See the included docs for how to configure it.
The code itself is pretty simple: it checks the variable and skips the
config job if appropriate (and everything else depends on the config job
already). There are two slight inaccuracies here:
- we don't insist on branches, so this likewise applies to tag names
or other refs. I think in practice this is OK, and keeping the code
(and docs) short is more important than trying to be more exact. We
are targeting developers of git.git and their limited workflows.
- the match is done as a substring (so if you want to run CI for
"foobar", then branch "foo" will accidentally match). Again, this
should be OK in practice, as anybody who uses this is likely to only
specify a handful of well-known names. If we want to be more exact,
we can have the code check for adjoining spaces. Or even move to a
more general CI_CONFIG variable formatted as JSON. I went with this
scheme for the sake of simplicity.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
15 lines
553 B
Plaintext
15 lines
553 B
Plaintext
You can configure some aspects of the GitHub Actions-based CI on a
|
|
per-repository basis by setting "variables" and "secrets" from with the
|
|
GitHub web interface. These can be found at:
|
|
|
|
https://github.com/<user>/git/settings/secrets/actions
|
|
|
|
The following variables can be used:
|
|
|
|
- CI_BRANCHES
|
|
|
|
By default, CI is run when any branch is pushed. If this variable is
|
|
non-empty, then only the branches it lists will run CI. Branch names
|
|
should be separated by spaces, and should use their shortened form
|
|
(e.g., "main", not "refs/heads/main").
|