Process: Automatically open PRs against upstream projects before/on release
@p-shahi is already working on this.
Since Nov 5, 2024.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
We used to have a section in the release process that talked about testing releases against upstream CI before releasing. That was removed, unfortunately, which has led to a few regressions (or, at least, broken tests): #2911, #2910.
However, now that we have the release flow, we should be able to completely automate this.
Idea:
1. When a draft release is published, open a draft PR against upstream projects using that draft release.
2. When a draft release is modified, update said PRs.
3. When a draft release is deleted, close those PRs.
4. When a final release is cut, open/update the upstream PRs to point to the final release (marking it as ready for review).
Ideally we'd find a way to link those PRs back to the release PR so we can track CI progress.
Projects we should check against (for now):
- [filecoin-project/lotus](https://github.com/filecoin-project/lotus)
- [go-libp2p-kad-dht](https://github.com/libp2p/go-libp2p-kad-dht/)
- [go-libp2p-pubsub](https://github.com/libp2p/go-libp2p-pubsub)
- [ipfs/kubo](https://github.com/ipfs/kubo)
- [ipfs/boxo](https://github.com/ipfs/kubo)
If this flow seems to work, there's no reason we can't add more projects later.
Contributor guide
No contributing guide indexed for this repository
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.