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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for automerging to happen when a subset of plans are successfully applied #4282

Open
1 task done
dimisjim opened this issue Feb 23, 2024 · 0 comments
Open
1 task done
Labels
feature New functionality/enhancement

Comments

@dimisjim
Copy link
Contributor

dimisjim commented Feb 23, 2024

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Describe the user story

We have a custom workflows setup in our org, in which we enforce repo-level configs such as the one shown here: #4280

Essentially, we want to plan for all affected envs, in any PR, but only apply for the one that matches the base branch.

We have achieved this using the workflows mentioned and linked above.

However, automerging doesn't work because all plans need to be merged for it to work.

This new feature would allow to bypass this, essentially making automerging work in our case.

Describe the solution you'd like

A flag, maybe something: --automerge-allow-partial-applied-plans that could be set to true, if the user desires.

Describe the drawbacks of your solution

this should be accompanied by a warning in the docs, as it would require the checks that we have implemented, or something similar

Describe alternatives you've considered

not use automerging at all

@dimisjim dimisjim added the feature New functionality/enhancement label Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality/enhancement
Projects
None yet
Development

No branches or pull requests

1 participant