replacing ci/config/allow-ref with a repo variable
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 15 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | ci: allow branch selection through "vars".github/ ci/ | +15 | 4 replies | |
| 2/2 | ci: deprecate ci/config/allow-ref script.github/ ci/ | +6 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] replacing ci/config/allow-ref with a repo variable
This is a more efficient way to do the same thing that ci/config/allow-ref does (which didn't exist back then).
We should be able to do the same with ci/config/skip-concurrent (and just use vars.CI_SKIP_CONCURRENT) throughout the workflow. But I didn't test that at all.
After that, the only useful thing left in the "config" job would be the "skip-if-redundant" step. I'm not sure if it will be possible to get the same behavior there without spinning up a VM.
[1/2]: ci: allow branch selection through "vars" [2/2]: ci: deprecate ci/config/allow-ref script
.github/workflows/main.yml | 10 +++++++--- ci/config/README | 14 ++++++++++++++ ci/config/allow-ref.sample | 27 --------------------------- 3 files changed, 21 insertions(+), 30 deletions(-) create mode 100644 ci/config/README delete mode 100755 ci/config/allow-ref.sample