-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for github 'bugrefs' #973
Conversation
18869bf
to
a705315
Compare
use Test::More; | ||
use Test::Mojo; | ||
use Test::Warnings; | ||
use Test::Output qw/stderr_like/; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is probably not required.
But it might make sense to merge this file with 16-utils-runcmd.t
anyways.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Deleted unused uses. But I don't want to merge with 16-utils-runcmd.t
which loads the database and is therefore way slower than 16-utils.t
which is only using the functions which don't need the database and is near instantly finished.
a705315
to
ba52f40
Compare
); | ||
my %bugurls = ( | ||
'https://bugzilla.novell.com/show_bug.cgi?id=' => 'bsc', | ||
$bugrefs{bsc} => 'bsc', | ||
$bugrefs{boo} => 'boo', | ||
$bugrefs{poo} => 'poo', | ||
'https://github.com/' => 'gh', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wondering why you didn't use $bugrefs{gh}
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably it differed during my development but does not anymore now. I will correct.
Add support for generic github repo markers as 'bugrefs Using the generic profile '<marker>[#<project/repo>]#<id>' for all bugrefs, especially for github, allows to track all issues reported on github and especially test fixing pull requests to be recorded as 'bugrefs' with the same icon as for "test issues", i.e. poo#. This way there is no need to create a ticket just to track a test issue for which already a github pull request exist because otherwise the URL to the github PR would not mean anything special to github and therefore not mark a job as "labeled". Also, pasting full github URLs is supported, same as for all other bugrefs, meaning that the URL is abbreviated into short form bugrefs. The pattern follows the openSUSE/OBS recommendation.
ba52f40
to
402ebd9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Add support for generic github repo markers as 'bugrefs
Using the generic profile
'[#<project/repo>]#'
for all bugrefs, especially for github, allows to
track all issues reported on github and especially
test fixing pull requests to be recorded as 'bugrefs'
with the same icon as for "test issues", i.e. poo#.
This way there is no need to create a ticket just
to track a test issue for which already a github
pull request exist because otherwise the URL to the
github PR would not mean anything special to github
and therefore not mark a job as "labeled".
Also, pasting full github URLs is supported, same as
for all other bugrefs, meaning that the URL is
abbreviated into short form bugrefs.
The pattern follows the openSUSE/OBS recommendation.