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

How to handle incarnation updates if a branch already exists #35

Open
defreng opened this issue Aug 22, 2022 · 0 comments
Open

How to handle incarnation updates if a branch already exists #35

defreng opened this issue Aug 22, 2022 · 0 comments
Labels
enhancement New feature or request foxops

Comments

@defreng
Copy link
Contributor

defreng commented Aug 22, 2022

If a foxops update branch and/or MR already exists, it is just ignored and no additional one is created - no matter the change in there.

That's suboptimal, because the owner of the incarnation is not notified that even more changes are pending and need to be addressed.

Multiple options exist:

  • create new MR based on previous pending MR
  • create new MR with all changes to main and close old one
  • update existing MR with new changes
@defreng defreng added enhancement New feature or request foxops labels Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request foxops
Projects
None yet
Development

No branches or pull requests

1 participant