From just a package developer point of view, I agree that the only thing that sounds effectively different from existing CompatHelper workflow is the automatic merge, which seems somewhat risky. CompatHelper opens a PR on a new branch with the right commit and tests will run as long as your CI is set to run on PRs. So the only step of the process that you are eliminating is the button click at the end. To have a fully automatic workflow, you’d need to automatically call Registrator as well for a new release.
tbeason
5
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Standard Git structure and update workflow for simple unregistered packages | 3 | 859 | May 11, 2021 | |
| Announcement: automatic merging for the General registry | 64 | 5142 | December 23, 2019 | |
| Are there tools to help with testing upper bounds on package dependencies? | 3 | 567 | January 30, 2020 | |
| How to deal with CompatHelper PRs on 1.7 | 0 | 527 | January 2, 2022 | |
| Further automation of CompatHelper | 1 | 384 | July 18, 2023 |