[Pulp-dev] Tracking issues for plugin_template

[David Davis]

Interesting. I did not know about this. Here's a link with more info:

https://docs.github.com/en/github/administering-a-repository/configuring-autolinks-to-reference-external-resources

David


On Fri, Apr 30, 2021 at 11:34 AM Ewoud Kohl van Wijngaarden <
ewoud+pulp at kohlvanwijngaarden.nl> wrote:

> On Sat, Apr 24, 2021 at 09:21:05PM -0400, Daniel Alley wrote:
> >On Fri, Apr 23, 2021 at 10:37 AM David Davis <daviddavis at redhat.com>
> wrote:
> >
> >> We started working on a plan to move repos over to Github Issues after
> >> PulpCon last year but I think it kind of fell by the wayside over the
> past
> >> few months due to how busy we've been with stakeholder work. It would
> >> definitely be a requirement in my mind to sort out things like how to
> link
> >> BZs to issues before moving plugins and other repos over to Gihub Issues
> >> that might have issues that affect downstream.
> >
> >I doubt there's any "good" way to link external bugs from Github because
> >Mozilla doesn't do so.  They just add an extra tag and you just have to
> >find the link somewhere in the comments.
> >
> >e.g.
> >
> https://github.com/servo/webrender/issues?q=is%3Aopen+is%3Aissue+label%3Abugzilled
> >
>
> If you're on a paid plan you can replace links to an external system. I
> can't find exactly where since it's hell to search for, but an example
> can be seen in https://github.com/puppetlabs/puppet where PUP-NNN links
> to their JIRA instance.
>
> It looks like it doesn't replace it everywhere as can be seen in a
> random PR: https://github.com/puppetlabs/facter/pull/2371
>
> Certainly this isn't great.
>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20210430/edb43cba/attachment.htm>