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

Block / delay staging per-repository #860

Open
xmo-odoo opened this issue Mar 25, 2024 · 0 comments
Open

Block / delay staging per-repository #860

xmo-odoo opened this issue Mar 25, 2024 · 0 comments
Labels
Projects

Comments

@xmo-odoo
Copy link
Collaborator

xmo-odoo commented Mar 25, 2024

Sometimes we want to block new stagings in order to do minor maintenance, or directly push programmatically generated commits which are low-risk but troublesome to merge via tooling e.g. translation updates (like odoo/design-themes@fdc593b).

Currently the handling is not great, the choices are basically:

  • push and then reset staging if any (or forget about it and then the staging is wasted because integrating to the branch after success fails)
  • or stop stagings gobally, which requires write access to crons, getting in between two runs of the staging cron check, and impacts more than just the branches we're concerned with

UX: a toggle button next to the branch, in the project form, probably

@xmo-odoo xmo-odoo created this issue from a note in Mergebot (accepted) Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Mergebot
accepted
Development

No branches or pull requests

1 participant