How do you use the Contributors page? #40454
Replies: 115 suggested answers 52 replies
-
|
The contributor role is best used for writers who are not a regular part of your team. Contributors can add new posts and edit and delete their own posts, but they can not publish them on your website, or edit or delete posts after they have been published. |
Beta Was this translation helpful? Give feedback.
{{editor}}'s edit
{{editor}}'s edit
-
|
I think this feature can be improved by hiding bots (maybe with an option) and showing humans only. EditAs @ghiculescu noticed here (make sure to upvote him, too) the contributors page says |
Beta Was this translation helpful? Give feedback.
{{editor}}'s edit
{{editor}}'s edit
-
|
How often do you use these graphs? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
How often do you use these graphs?
Do you explore these graphs in your own repositories, or for other repositories?
What data are you looking to get from it?
|
Beta Was this translation helpful? Give feedback.
-
Would love to add metrics around code reviews. High quality code reviews are essential contributions to a healthy project. |
Beta Was this translation helpful? Give feedback.
-
|
How often do you use these graphs? Do you explore these graphs in your own repositories, or for other repositories? What data are you looking to get from it?
What actions do you expect to take using the data from this page? What could we do to make this data easier or better for you?
Anything else you think we should know? |
Beta Was this translation helpful? Give feedback.
{{editor}}'s edit
{{editor}}'s edit
-
|
It would be really cool to be able to see contributes broken down by week. I want to be able to see how much code was added/deleted by each member on a given week. |
Beta Was this translation helpful? Give feedback.
-
|
It would be useful to have an overview of the amount of lines per contributor that are still mostly present in the latest commit on the main branch, so that you know who (presumably) knows most about the current codebase. Especially useful for large refactors. |
Beta Was this translation helpful? Give feedback.
-
Trying to gauge how active a project is and how many contributors are active
Maybe some filters:
Github is probably in a good position to detect projects that are critical to OSS "public infrastructure" and maintained by a small number of contributors in their spare time => could decide to improve visibility on such cases and help critical maintainers attract support (either through PR or financial). |
Beta Was this translation helpful? Give feedback.
-
|
I'm using it mostly on work repositories to get a sense of trends - like if we're slowing down or not in terms of work done etc as a rough indicator of how we're doing. |
Beta Was this translation helpful? Give feedback.
-
|
I hope have a search Contributors function in Insights |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I'd like to see more than the top 100 contributors. I like seeing myself on the list and I'm sure I'm the 101st contributor on many of the repos I've committed too. Top contributors this year/month/week would also be good. |
Beta Was this translation helpful? Give feedback.
-
|
What could we do to make this data easier or better for you?
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I stopped showing up in the contributors analytics for all repos. Can someone investigate? https://github.com/mikestaub/serverless-express/graphs/contributors |
Beta Was this translation helpful? Give feedback.
-
|
I use it simply for the activity graph, so I can see the quality of a repo's maintenance. Now I do NOT expect the graph to be as high in later years as at the start of the project, but I do expect to see activity, and especially, activity by contributors who have been contributing for a looong time, selflessly, through thick and thin. I'd expect a sort of gamma distribution shape of cumulative activity, punctuated with small bursts of activity later on when big new features or refactors are implemented, and with certain contributors staying the course. Here is something you might want to look at. As the rate of "stars accumulation" declines, do the main contributors lose interest, or do they persevere? That would be a very good sign, IMO, that they're in it for the long haul, that they have staying power and conviction, which indicates that the repo/project is going to be safe to use and contribute to. |
Beta Was this translation helpful? Give feedback.
-
Once every or every two weeks.
Mostly repositories I contributed to, but also other repositories.
Most active developers and their contributions, recent activity to determine whether the repository is still maintained.
Conctact certain developers, potentially decisions for sponsoring.
Remove certain generated (lock-)files from the contribution stats as they do not represent real work. See also #15148
No. |
Beta Was this translation helpful? Give feedback.
-
|
Good job 👍🏼 |
Beta Was this translation helpful? Give feedback.
-
|
How often do you use these graphs? What data are you looking to get from it? What could we do to make this data easier or better for you? I would love to see a score or some kind of grade about the "quality" of the package. If the development / bug fixing is regular, should get higher score. More active developer the score could be higher, etc... Good example for package quality scoring is the emberobserver.com package scoring, ex: https://emberobserver.com/addons/ember-cli-typescript |
Beta Was this translation helpful? Give feedback.
-
Monthly.
Both.
Who contributes the most as a proxy for who is leading the project, as well as who I might contact to discuss the project.
I might contact a developer using the information on the page to discuss the project.
I would love for bot account commits to be removed from contribution counts or at least the ability to disable counting them would be great.
Nope! |
Beta Was this translation helpful? Give feedback.
-
|
I use it rarely. But when looking for open source projects and libraries to use in my developments I sometime use it to get an idea of how many contributors are there, how often do they commit, how many are currently active and is the main contributor still very active or dormant. It does a good job at that. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Sir, IP address: I need to execute SQL select queries from Playbook. Please help me in this. I need your help sir. Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
How often do you use these graphs?
|
Beta Was this translation helpful? Give feedback.
-
|
Could be improved by adding a way to specify what files/folders to ignore when computing contributors stats (same as See the problem here: GitHub contributions page shows too many changes. The accepted answer does not solve the problem, even for the author of the answer. |
Beta Was this translation helpful? Give feedback.
-
Every now and then, call it monthly.
My own.
Team performance. Finding people who are worthy of callouts. Seeing if people are managing to ship code (particularly useful at a birds eye view for new hires).
Encouragement and/or more direct help, as appropriate.
Here is what our graph looks like: Can you guess where we enabled squash as the only permitted merge strategy for PRs? I realise this might be beyond the scope of the feature but it would be amazing if the graph could get flattened out somehow to account for this. |
Beta Was this translation helpful? Give feedback.
-
Would be cool if you could see the number of lines that are still in the codebase, rather than just a sum of the diffs. Right now I can just re-write the same line 1000 times and it show as +1000/-1000. Might be too much to compute regularly for some repos, but can't hurt to ask? |
Beta Was this translation helpful? Give feedback.
{{editor}}'s edit
{{editor}}'s edit
-
|
Feels like the Insights area has sooo much potential for maintaining good technical and operational health on teams whilst letting them manage it autonomously. There's some data that's just difficult to get at right now and some data that third-parties are charging a lot of money to provide from Github's data.
For context, I'm an Engineering Manager. So I'm keen to keep our tech and operations healthy using this data and also use it to help people develop. Answered the questions you had below.
|
Beta Was this translation helpful? Give feedback.



{{editor}}'s edit
{{editor}}'s edit
-
Select Topic Area
Product Feedback
Body
Feedback we'd love to hear from you
Beta Was this translation helpful? Give feedback.