Checkout PR on top of latest `master`/`main` branch
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.9k
- Forks
- 2.8k
- PR merge metrics
- No merged PRs in 30d
Description
Hey, this is a feature request which may be useful from a test-strategy perspective. We could add an option to allow applying the PR patch to the latest master branch instead of just checking it out. This would allow us to verify the change after it has been merged on top of the latest master before actually merging it.
Surely, it would be an optional feature which should be disabled per default.
Contributor guide
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 files or tests are named. Start by examining how the checkout action currently selects and checks out a ref, then define the optional, default-disabled behavior for applying a pull request to the latest master or main branch. Done should include a documented configuration option and verification that existing checkout behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100