#434: Contributing to a pagure repository
-------------------------------------+-------------------------------------
Reporter: robyduck | Owner:
Type: New badge | robyduck
idea | Status:
Priority: major | reopened
Keywords: | Resolution:
Has a description: 1 | Has a name:
Artwork status: Approved | 1
(design team members only) | Concept approved (reviewers only):
External requirements: | 1
Triaged (triagers only): 1 | Badge definition status:
| Full, needs review
| Manually awarded:
| 0
-------------------------------------+-------------------------------------
Comment (by sayanchowdhury):
Replying to [comment:32 lsedlar]:
The message format from Pagure has changed in the past I believe. I
have
attached a patch that may fix the problem and only works with the current
format.
There are three places in the message with some name:
* {{{msg.agent}}} is the person who pushed the commits
* {{{msg.repo.user.name}}} is owner of the repo that was pushed to
* {{{msg.authors[].name}}} is a list of people who wrote the pushed
commits
My patch is using the first of these, as there there is no way to map
individual
authors to commits they wrote. It will also accumulate the
number in msg.total_commits.
Yes, the older format of the Pagure fedmsg message included
the number of
commits per author. If the {{{msg.agent}}} is given the given the badge
then it will only be the admins who will get the badge. So, I think its
worth waiting for the hook or if the hook takes time then we just push
this patch for now. Thoughts?
--
Ticket URL: <
https://fedorahosted.org/fedora-badges/ticket/434#comment:35>
fedora-badges <
https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app