Contibuting changes upstream
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
Research direction
Start by reviewing the changes in PR #1, the discussion in issue #26, and the earlier upstreaming attempt in PR #147. The work is done when the relevant improvements are agreed with maintainers and prepared as an accepted upstream pull request.
Written by the indexing model from the issue text.
Description
Hi there folks 👋
This fork has few really nice fixes and improvements in it. The one in particular that stands out is the fix for 'lost commits' in PR #1 which is a continuing topic of discussion here: https://github.com/telia-oss/github-pr-resource/issues/26
Have you folks considered trying to get these changes merged upstream so that others could take advantages of the improvements in telia-oss/github-pr-resource (from what I understand the 'main' repo) while also leveraging some of the excellent work here?
I see that @christophermancini opened a PR last year to try and upstream changes in PR #1 but the PR seems to have withered a little and I'm getting 500 errors just trying to open it. https://github.com/telia-oss/github-pr-resource/pull/147
Would be happy to contribute to the work of preparing PRs to bring the two projects closer together if you folks might be interested and could provide a little support and guidance.
Any help appreciated.
Thanks for sharing!
- Dominant language
- Go
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·