stacks-network / stacks-network/stacks-core
[CI] Fix CI setup to not reuse a cache if the destination branch changes on a PR
Open
@wileyj is already working on this.
Since Dec 13, 2023.
bug
CI
- Dominant language
- Rust
- Stars
- 3.1k
- Forks
- 762
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 76
Description
Describe the bug
Currently CI avoids fully re-running based on commit sha to enable build reuse. However, this does not account for destination branches changing. So if you open a PR against branch A and it builds, but then you change to against branch B, it will reuse the archive as it has the same commit hash. However, it should rebuild and fully rerun in this scenario. Update it to do so.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.