edf80d23f1
Now that we have the CI_BRANCHES mechanism, there is no need for anybody to use the ci/config/allow-ref mechanism. In the long run, we can hopefully remove it and the whole "config" job, as it consumes CPU and adds to the end-to-end latency of the whole workflow. But we don't want to do that immediately, as people need time to migrate until the CI_BRANCHES change has made it into the workflow file of every branch. So let's issue a warning, which will appear in the "annotations" section below the workflow result in GitHub's web interface. And let's remove the sample allow-refs script, as we don't want to encourage anybody to use it. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com> |
||
|---|---|---|
| .. | ||
| README | ||
README
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").