Skip to content

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

@defreng

Description

@defreng

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions