Commits on branches should count towards profile contributions

[tammymogul]

Select Topic Area

Product Feedback

Body

This has been an ongoing challenge with Github for 10+ years. I've historically had teams that do a lot of research work on branches, which often never get merged to the main branch and that's good and expected. However when you look at those profiles, you would think they haven't been doing any work at all.

I think the policy of only counting contributions when they are merged into the main branch needs to be reconsidered. Work on a branch is still work, and it should be counted.

[hades255]

I think that is not necessary.
When you done pull request, perhaps delete that branch.
So why branch history needed?

[KashanSiddiqui]

Agree on the problem, there have been alot of devs working on branches for different needs and we often deploy branch on subdomains while team continue to work for major features on main branch. By the looks of graph it shows the devs never worked in that time.

[pantharshit007]

I am not sure but from what I know commits from branches (even your own repos) when merged should be counted as n commits not 1 merge commit.

[ktsreddy007]

Hi @tammymogul

If branch is temporary which we delete once after merged so i think we should not take branch into consideration , Instead i think they need to take PR as consideration like how many valid PR will be triggered by Dev and based on approved PR's count only the contributions count should be taken into consideration what do you say about it ???.