Contibuting changes upstream

Open
#16 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
ci-cd

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.