managedkaos / managedkaos/merge-pull-request
Add beneficial code from forks
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
These forks have updated the action with some cool features:
- [argyle-engineering/merge-pull-request](https://github.com/managedkaos/merge-pull-request/compare/main...argyle-engineering:merge-pull-request:master): adds `fetch-depth` parameter to 0 allows the action to run agains the head commit in the PR and do the necessary merge.
- [seblaporte/merge-pull-request](https://github.com/managedkaos/merge-pull-request/compare/main...seblaporte:merge-pull-request:master):
- renames `BRANCH_TO_MERGE` to `BASE_BRANCH`
- uses `.pull_request.base.ref` instead of `.pull_request.head.ref`
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
Start by reviewing the repository's GitHub Action entry point and the two linked fork comparisons. Incorporate the relevant fetch-depth and base-branch behavior, then verify that the action still merges pull requests correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100