The Autolink feature[1] is enabled[2] now. This helps in seamless integration and switching between jira and commits.
Only the following type of tagging work What works: - SYSTEMDS-1234 - SYSTEMS-1234, SYSTEMDS-1235 What won't work: - SYSTEMDS-1234-1236 - SYSTEMDS-1234-36 - SYSTEMDS-1234,1235 [1] https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/configuring-autolinks-to-reference-external-resources [2] https://issues.apache.org/jira/browse/INFRA-22054 Regards, Janardhan On Tue, Jun 29, 2021 at 2:16 PM Mark Dokter <mdok...@know-center.at> wrote: > > > On 29.06.21 08:38, arnab phani wrote: > > Thanks. This is good. > +1 > > However, I don't think we need it right now. We tend to encode more > details > > in the commit message than in the jira task. > > Therefore it would be all the more valuable if that feature can also > insert a link back from the JIRA ticket to the commit so there is a link > from the JIRA ticket, where issues should be documented to the git > history where things are actually documented :P > > > Regards, > > Arnab.. > > > > jm2c, Mark > > > On Sat, Jun 26, 2021 at 4:18 PM Janardhan <janard...@apache.org> wrote: > > > >> Hi all, > >> > >> To navigate between the jira numbers in the commit messages > >> there is an autolink[1] feature on GitHub enterprise (@apache has > >> enterprise license). > >> > >> Issue key (like, SYSTEMS-2015) will be linked > >> to https://issues.apache.org/jira/browse/SYSTEMDS-2015 > >> > >> To see an example, checkout spark repository[2]. > >> > >> What do you think about this, shall we add this feature? > >> > >> [1] > >> > >> > https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/configuring-autolinks-to-reference-external-resources > >> [2] https://github.com/apache/spark > >> > >> Thank you, > >> Janardhan > >> > > > >
