Support autolink reference configuration in the API

GitHub Ecosystem
,
#1

The Autolink References feature is very useful, but only configurable at a repository level. Since there’s no org-level support, this makes it very difficult to use/keep up to date for multiple links (such as to support multiple projects in JIRA) across all of an org’s active repos.

There’s a suggestion for enabling it at the org level - but allowing us to update the list of links via the github apps API would solve the problem from a different angle, and would allow us to automatically keep the list up to date with all the links we may wish to support.

50 Likes
#2

Very similar to https://github.community/t5/GitHub-API-Development-and/Enable-automatic-branch-deletion-for-repository-with-api/m-p/31327#M2925

#3

Is there an API support for Autolink references yet ? :grin:

#4

At the moment there isn’t a way to configure auto-link references via an API. We’ve had several requests for this, and have an internal issue open tracking interest. I’ve added you as an interested party.

2 Likes
#5

I’m interested as well (so that the terraform provider can support this functionality).

1 Like
#6

Thanks for the reply :slight_smile:

1 Like
#7

Also interested for downstream terraform support. https://github.com/terraform-providers/terraform-provider-github/issues/285

2 Likes
#8

I’m quite interested in this feature. Applying these settings to a fairly large codebase manually is… painful.

2 Likes
#9

Chiming in my support for this as well, we’re an organization of 1.8k+ repos so manually configuring this setting is, not ideal :stuck_out_tongue:

1 Like
#10

I’m interested in thsi feature.
We have multiple projects on JIRA and adding autolinks for all those is not ideal.

#11

I’m also interested to configure this feature via api in my company.

#12

I’m also interested!

#13

Thank you all for your feedback, I’ve your +1 to our internal issue! I hope to be able to bring some news soon.

#14

as the maintainer of https://github.com/probot/settings, i’d love to be included in your internal tracking for this (and other API functionality that enables management of repo settings through the api). we have an issue requesting this functionality for settings here: https://github.com/probot/settings/issues/187, but require availability through the API before we are able to implement on our end.

1 Like
#15

Thanks for linking the issue @travi, I’ll be sure to link it. And welcome to the community.

1 Like