Releaseable using wrong URLs in "status" message
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/Raku/whateverable/blob/main/xbin/Releasable.p6#L223
Generates gists like https://gist.github.com/Whateverable/0e6ddedaa715a2cb0eebf0c5278016ec
Which have URLS like
https://github.com/rakudo/rakudo.git/commit.git/d6dda7eb4c5744cecaa10aefac81bd5eb1f44293
Which are incorrect - the '.git' doesn't resolve here - it only redirects to rakudo/rakudo if you end at rakudo/rakudo.git - if you add the commit after it, that no longer redirects and instead 404s.
Should be https://github.com/rakudo/rakudo/commit/d6dda7eb4c5744cecaa10aefac81bd5eb1f44293
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
Inspect xbin/Releasable.p6 around line 223, then review the generated gist linked in the issue to trace how repository URLs are assembled. Update the status links so commit URLs omit the repository's .git suffix, and verify they resolve to the expected GitHub commit page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- backend, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100