I imagined for downstream Bugzilla for example, we would have the
downstream BZ link to the upstream using the tracker ggainey mentioned.
Then for the github issues we would have a 'Bugzilla' label, and the link
would be in the comments. I expect the scripts would ensure these were
present like the
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+p...@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 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 b
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
On Fri, Apr 23, 2021 at
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 i
On Thu, Apr 22, 2021 at 6:48 AM Ina Panova wrote:
>
> On Wed, Apr 21, 2021 at 7:55 PM David Davis wrote:
>
>> Wanted to bump this to hopefully get some feedback. Also, today during
>> our CI/CD meeting we discussed also tracking issues for pulp-oci-images on
>> github as well.
>>
>> If there are
Regards,
Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where there is no path and leave a trail."
On Wed, Apr 21, 2021 at 7:55 PM David Davis wrote:
> Wanted to bump this to hopefully get some feedback. Also, today during our
Wanted to bump this to hopefully get some feedback. Also, today during our
CI/CD meeting we discussed also tracking issues for pulp-oci-images on
github as well.
If there are no objections by next week April 26, I'll assume I can proceed
with moving these projects' issues over to Github.
David
I've always felt that tracking plugin_template issues under the main pulp
project in plan.io was suboptimal and with other repos such as pulp-cli
moving to github issues, I feel that it might make sense for the
plugin_template to move to github issues as well.
There's only 11 open issues right now
