This change is split out from #20697 as requested by MarcoFalke, and allows using lint task in forked repos with personal Cirrus CI accounts.
Based on #20697, only the last commit should be reviewed.
ci: Fix COMMIT_RANGE variable value for cloned repos #20717
pull hebasto wants to merge 4 commits into bitcoin:master from hebasto:201218-clone changing 6 files +5 −36-
hebasto commented at 5:05 PM on December 18, 2020: member
-
4d0df3f68a
ci: Fix COMMIT_RANGE variable value for PRs
Co-authored-by: MarcoFalke <falke.marco@gmail.com>
-
ci: Drop Travis-specific way to set COMMIT_RANGE variable fee0f9db37
-
ci: Drop Travis-specific workaround for shellcheck 143c6e10e0
-
ci: Fix COMMIT_RANGE variable value for cloned repos ec9931dbe7
- DrahtBot added the label Tests on Dec 18, 2020
-
DrahtBot commented at 3:19 AM on December 19, 2020: member
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Conflicts
Reviewers, this pull request conflicts with the following ones:
- #20697 (ci: Fix COMMIT_RANGE variable value by hebasto)
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
- hebasto closed this on Dec 19, 2020
- hebasto reopened this on Dec 19, 2020
-
hebasto commented at 9:00 AM on December 19, 2020: member
@MarcoFalke Any hint why Cirrus CI is not triggered by this pull?
- hebasto marked this as a draft on Dec 19, 2020
- MarcoFalke marked this as ready for review on Dec 19, 2020
- MarcoFalke closed this on Dec 19, 2020
- MarcoFalke reopened this on Dec 19, 2020
-
MarcoFalke commented at 9:55 AM on December 19, 2020: member
Sorry, no. Though, this has to wait on #20697 anyway
- hebasto marked this as a draft on Dec 19, 2020
-
- hebasto closed this on Dec 20, 2020
- fanquake locked this on Feb 22, 2021
- hebasto deleted the branch on Feb 28, 2021
Contributors
Labels