Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support pushing to a derived branch, but in the main repository #83

Open
jelmer opened this issue Oct 2, 2022 · 0 comments
Open

support pushing to a derived branch, but in the main repository #83

jelmer opened this issue Oct 2, 2022 · 0 comments
Labels
janitor.kali.org To do with the Kali Janitor instance

Comments

@jelmer
Copy link
Owner

jelmer commented Oct 2, 2022

See https://salsa.debian.org/jelmer/debian-janitor/-/issues/156 for background

It would be useful to support new publishing modes that function like push_derived and propose, but create a branch in the original repository rather than in the bots repository. Maybe this should be a flag in the publishing policy rather than altogether different modes - "derived_branches_in_origin: true" or something like that.

For example, it could create a "merge-upstream/3.3" branch in the main packaging repository that the maintainer can then easily find and pull into the main packaging branch at their own leisure.

Most of this is straightforward on the janitor/silver-platter side. The main challenge is around garbage collection - we'd presumably want to clean up these branches when they become obsolete.

See jelmer/silver-platter#15 for the matching silver-platter bug report - which is where the core logic should be.

@jelmer jelmer added the janitor.kali.org To do with the Kali Janitor instance label Oct 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
janitor.kali.org To do with the Kali Janitor instance
Projects
None yet
Development

No branches or pull requests

1 participant