Skip to content

Investigate ways to reduce the need to rebase after each merge #2591

@perdasilva

Description

@perdasilva

Description

As a contributor I don't want to keep having to rebase my PR everytime master changes. We should investigate if there are ways to reduce this requirement while still protecting the master branch from breaking

Acceptance Criteria

  1. Document outlining options with pros/cons
  2. Document presented during WG meeting for feedback
  3. Additional storie(s) in the backlog to implement the solution

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.story

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions