Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
proposal: introduce new html meta tag for issue trackers #19725
For the users of the packages with vanity import paths uses, it is often impossible to find the package's issue tracker to file an issue. The package maintainers often have to manually add a link to the package comment to ensure that users will be able to find the package's issue tracker. This process is tedious and adding more noise to the godoc.
I propose to introduce a new meta tag for our vanity URL redirect pages, so that the package owners can set the location of the package's issue tracker.
Once a meta tag is introduced, the Go tools (such as godoc.org) can display a link to the issue tracker on the package page.
I don't have much data around this.
Some more questions... Source may live somewhere else but the issue tracker might be on GitHub. Source may live on GitHub but issue tracker may not not. How many providers should we support? Do we want to auto identify issue trackers by looking at the source? Is that expected by the the package maintainer that we automatically show an issue tracker link?
Suggesting a meta tag is the most conservative approach I could think of, that's why I kept the proposal very limited to a specific case.