The new custom autolink references feature is very nice, but it would be better if an autolink reference could be configured at the organization level so that all repos under an organization could utilize them.
Thanks for this feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.
Thanks! Count us as an enterprise subscriber also very interested in this. Let me know if submitting a ticket through enterprise support would do anything to increase its priority.
Ditto! I also want to add autolink references at an org level.
This is something we would like as well. We use autolink references to link out to JIRA tickets
Our JIRA projects to no 1-1 align with Github Repos. Having to configure and maintain the same auto links references in each repo becomes painful by hand.
I’d also settle for being able to manage these in code similar to how the CODEOWNERS file works
+1 would be happy to see it in our GHE.
Ditto! Also interested
i havent gone to the link yet but im pretty possiyive it would have helped out a lot 2 years ago when i first started this issue
Is there any progress on this?
Same here. We have about 4 or 5 Jira projects we use. What a huge pain to have to duplicate the auto-links across 50+ repositories (and possibly 50 - 100 more in the next year).
Agree. It’d be super nice to have this feature. Any update?
would be really helpful!
+1 for this, and it would also be very useful if this was configurable as code (through a
.github repository) rather than only through the UI.
+1 for support to define this at the Org level would be most helpful as we have several and they each have their own set of references they would like to have.
Much needed in today’s microservice multirepo architecture
this is a very required feature
+1 this, and/or API support is definitely a must-have
+1 - also being able to map multiple prefixes to one Target URL would be a nice QOL improvement, e.g.:
+1 … this request has over 100 likes, is over 18 mo old, so I’m hoping my vote throws those that can make this happen into action!