-
Notifications
You must be signed in to change notification settings - Fork 15
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
New kwalitee metric: link to repository #16
Comments
Also for each other known (non-x_) subfield? Or for +1 for |
I wondered whether MetaCPAN treats the bugtracker as github if it sees a github repo (in which case this check should also require you to specify a bugtracker, if you specify a repository), but no: it sticks with RT unless you explicitly tell it another bugtracker. One could still argue that if you specify a repo, then you should specify a bugtracker, but I won't push that one too hard :-) |
Most probably because It's too tedious to migrate all of the existing RT tickets to github issues :p I have mixed feelings about a bugtracker resource because I sometimes need to look for a link to RT for a distribution whose resources.bugtracker points to github issues, to see old tickets. |
The configuration for a github repository allows one to disable the "Issues" feature. So it should not be assumed by default that a github repository uses the github issue tracker. |
The META spec defines the resources key.
CPANTS players should get extra points when having
resources.repository
in their META file.The text was updated successfully, but these errors were encountered: