submit: use terminal links
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
Read internal/style/style.go at the Hyperlink function and compare it with the existing update notice in cmd/submit.go. Trace the new-PR output in gh stack submit, then ensure its PR URL uses the same terminal-link behavior and verify the resulting output.
Written by the indexing model from the issue text.
Description
The output when gh stack submit creates a new PR looks like this:
=== Phase 3: PRs ===
✓ Created PR #1234 for boneskull/derp (https://github.com/boneskull/derp/pull/1234)
This should instead use the Hyperlink function:
gh stack submit uses this function when emitting a notice about updating a PR; see:
- Dominant language
- Go
- Stars
- 9
- Forks
- 2
- Avg merge
- 9h 14m
- Merged PRs (30d)
- 8
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.
More from boneskull/gh-stack
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
performance
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in boneskull/gh-stack
Similar issues
-
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 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100