Is there any way we could add automation to help us here? Like can we have
a script to file the issue automatically if there is no issue for a new PR?
- Ken
On Fri, Nov 22, 2019, 5:21 AM Tomas Kopecek <tkopecek(a)redhat.com> wrote:
Hi,
in last few months there is a quite a lot of PRs without issues and/or
linked properly.
If you're filing a PR for koji, it would be very helpful if:
a) Create an issue first
b) link PR to this issue - for this to be working correctly, you need to
reference it in commit (not in PR's comment) via standard pagure keywords
[1] <
https://docs.pagure.org/pagure/usage/magic_words.html>. So,
typically via line:
"Fixes:
https://pagure.io/koji/issue/1725"
<
https://pagure.io/koji/issue/1725> as in [2]
<
https://pagure.io/fork/tkopecek/koji/c/3ee3ea7acd31f41950e717ba3af9adc4d8...
. <
https://pagure.io/koji/issue/1725>
Creating an issue improve visibility of PR in the team (It can be planned
to roadmap, etc.). Using proper "Fixes" keyword will help us in navigating
in pagure.
It is not a hard requirement (I will be happy for all PRs even without
issues or links), but will alleviate us from some routine work when
grooming and merging those PRs.
Thank you all!
[1]
https://docs.pagure.org/pagure/usage/magic_words.html
[2]
https://pagure.io/fork/tkopecek/koji/c/3ee3ea7acd31f41950e717ba3af9adc4d8...
--
Tomas Kopecek <tkopecek(a)redhat.com>
Release Engineering Development, RedHat
_______________________________________________
koji-devel mailing list -- koji-devel(a)lists.fedorahosted.org
To unsubscribe send an email to koji-devel-leave(a)lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/koji-devel@lists.fedorahoste...