Don't invalidate CR or QA stamps for clean master merges
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37
- Forks
- 10
- Avg merge
- 5d 4m
- Merged PRs (30d)
- 1
Description
Provide a configuration point which enables clean master merges to be pushed to a branch without invalidating the existing CR or QA stamps.
This is helpful when working with a repository with the "Require branches to be up to date before merging" setting enabled:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating the handling of clean master merges and the logic that invalidates CR or QA stamps, then identify where a configuration point can preserve those stamps; done means the option allows clean master merges without invalidation while existing behavior remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100