💅 Add a config for the Patchback GitHub App#12475
Conversation
This patch prepares the project's backporting process to start being handled by the Patchback GitHub App [[1]]. Ref pytest-dev#9384 Resolves pytest-dev#9385 Resolves pytest-dev#9553 Resolves pytest-dev#9554 Resolves pytest-dev#9555 [1]: https://github.com/apps/patchback
|
Thanks @webknjaz, do we have any documentation on how the patchback works? I assume we just apply the "backport" label at any moment in the PR lifetime, and once it gets merged, it will open a PR backporting the merged change to the correct branch? |
|
Should we also remove https://github.com/pytest-dev/pytest/blob/main/.github/workflows/backport.yml? |
Not yet. Ronny and I agreed to keep it for a while. |
Not really, but the source code is pretty clear, I think.
Yep, that's it. It should be a drop-in replacement with no change in how it's used (except for having a few more features than the current workflow). |
|
For this, install https://github.com/apps/patchback/installations/new/permissions?target_id=8897583&target_type=Organization. You should't need to wait until the PR is merged. |
nicoddemus
left a comment
nicoddemus
left a comment
There was a problem hiding this comment.
Thanks @webknjaz for the info!
Backport to 8.2.x: 💚 backport PR created✅ Backport PR branch: Backported as #12480 🤖 @patchback |
…7b401063874141fcbcda78eaec3c28148e7dcd8/pr-12475 [PR #12475/d7b40106 backport][8.2.x] 💅 Add a config for the Patchback GitHub App
Previously, this workflow was being used to cherry-pick PRs made against `main` into older stable branches. Now that pytest-dev#12475 integrated the Patchback GitHub App, it's no longer needed as it's making duplicate pull requests which don't even trigger CI runs automatically due to pytest-dev#10354. So this patch removes said workflow to address the problem.
|
Thanks for fixing this, the old setup was quite annoying :) |
This patch prepares the project's backporting process to start being handled by the Patchback GitHub App [[1]]. Ref pytest-dev#9384 Resolves pytest-dev#9385 Resolves pytest-dev#9553 Resolves pytest-dev#9554 Resolves pytest-dev#9555 [1]: https://github.com/apps/patchback
Previously, this workflow was being used to cherry-pick PRs made against `main` into older stable branches. Now that pytest-dev#12475 integrated the Patchback GitHub App, it's no longer needed as it's making duplicate pull requests which don't even trigger CI runs automatically due to pytest-dev#10354. So this patch removes said workflow to address the problem.
|
No problem! I would've done this earlier if it was greenlighted.. |
webknjaz
added
the
type: infrastructure
4 participants
This patch prepares the project's backporting process to start being handled by the Patchback GitHub App [1].
Ref #9384
Resolves #9385
Resolves #9553
Resolves #9554
Resolves #9555