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
- Document outlining options with pros/cons
- Document presented during WG meeting for feedback
- Additional storie(s) in the backlog to implement the solution
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
masterbranch from breakingAcceptance Criteria