Skip to content

Merging/reviewing a PR as contribution #17

Open
@betatim

Description

@betatim

Following on from #13 and https://github.com/choldgraf/github-activity#how-does-this-tool-define-contributions-in-the-reports

Did we already discuss why someone who merges a PR isn't listed as a contributor? Is that covered because they comment on a PR (PRs == issues?)

It seems unlikely that somehow who can/does merge PRs wouldn't also full fill the other criteria so the net result of this would be zero. However listing the "rules" for how to qualify as contributor will incentivise people to take those actions (all metrics will get gamed, etc). In those case it would be a good thing because people will start doing the stuff that helps move the project forward. Which made me think: getting PRs reviewed/merged is one of the biggest bottlenecks ... can we get people to help here by explicitly listing it as a to contribute?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions