golang/go

x/build: rewrite Hg hashes in issue tracker

Open

#21,088 opened on Jul 19, 2017

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
BuildersNeedsFixhelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Some old issues refer to mercurial hashes in their issue tracker. There is a mapping at https://golang.org/change/XXXXX and the git commits have this data too (as a golang-hg header in the commit), but if you don't know that it can be hard to track down.

Instead of people having to know this, one could rewrite all codesite URLs in the issue tracker to become googlesource.com URLs.

example: https://github.com/golang/go/issues/2516 mentions http://code.google.com/p/go/source/detail?r=4e38cad33649.

Contributor guide

Research direction
Inspect the mapping of mercurial hashes to git commits and update references in issue comments.
Tech stack
go
Domain
build systemdevops
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65