GitHub Community
How do you use the Contributors page? #40454
Replies: 237 comments 105 replies
-
|
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.
-
|
I think you should be able to remove a contributor, like in my case, where an individual made a seemingly helpful contribution but the contribution turned out to be conniving and the contribution was ultimately removed. Thankfully, in my case, it was a minor contribution. However, the individual is still visible as a contributor, which devalues the repo's integrity in my opinion. If there is an option to remove a contributor from a personal repo, I have not found it. |
Beta Was this translation helpful? Give feedback.
-
|
Ok |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, clicking and dragging in the graph is not a good UX. I most often want to look at the current year, and in a 10 year old repo that is quite hard to get exactly right. A "this year" preset would be amazing. |
Beta Was this translation helpful? Give feedback.
-
|
How often do you use these graphs? |
Beta Was this translation helpful? Give feedback.
-
Today I learned, and I've been using this particular feature for a long time. If I've missed that feature, I think a lot of other people are unaware of it too. |
Beta Was this translation helpful? Give feedback.
-
|
It might be nice to have presets like 30 days, 60 days, etc. as well, to quickly measure common ranges. |
Beta Was this translation helpful? Give feedback.
-
Yeah, clicking and dragging in the graph is not a good UX. I most often want to look at the current year, and in a 10 year old repo that is quite hard to get exactly right. A "this year" preset would be amazing. |
Beta Was this translation helpful? Give feedback.
-
|
Using it on a regular basis for our own repos, out of curiosity, but also to update our contributors pages in the (FOSS) app. Presets like "current year" or "last twelve months" would help (but are not a "must-have" for us). |
Beta Was this translation helpful? Give feedback.
-
|
The clicking and dragging on the specific date range is super annoying. I like to look at particular ranges. For example over the whole year - really annoying to try and line up the graph to a specific date. Just let me type my date! |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I agree with these answers, one addition is that I'd like certain generated (lock-)files to be ignored from the contributions stats as mentioned in #15148 |
Beta Was this translation helpful? Give feedback.
-
|
Not just lockfiles, if there is a way to exclude most (all) generated code this would remove a lot of the clutter. For example all code that was generated automatically after running Currently, in repos where generating files is common, these graphs are completely useless. Maybe just counting the actions and not the loc would help, similar to the diagram on the profile page, just as a graph. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe add a feature that allows us to exclude certain folders where the generated files are, e.g. |
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.
-
|
My opinion about the page is exactly the same. I find "Contributors" page VERY informative speaking about choosing a maintained solution for my projects. |
Beta Was this translation helpful? Give feedback.
-
|
This is pretty much my evaluation ( though I use it more like bi-weekly ). When evaluating other projects I:
|
Beta Was this translation helpful? Give feedback.
-
|
Raffle key girh |
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.
-
I suspect these vary too wildly across teams, although big corporate might like the free promotion towards enterprise features. |
Beta Was this translation helpful? Give feedback.
-
|
I second and third this. @adlai @rmathew1992 i think that commit only metrics around contributions is really not presenting the full picture. i have a specific example However if you look at the PR's you can see we have many people leaving comments and in line commits sometimes (but not always). pyOpenSci/python-package-guide#14 I think issues are contributions too. But on pr's i'd say review feedback as it valuable as direct commits. If github could capture these types of non commit based metrics it would be invaluable to growing communities like ours. while this might be difficult you could capture total # of unique contributors across issues and prs and then on pr's maybe both commits AND review comments as being contributions is an idea. +1000 to the comment above!!! |
Beta Was this translation helpful? Give feedback.
-
|
i think that commit only metrics around contributions is really not presenting the full picture. |
Beta Was this translation helpful? Give feedback.
-
|
Contributions Commits should not be the default metric, it's pointless. |
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.
-
You can select a subrange on the main graph and it filters the data underneath --- discoverability problem with the ux i guess |
Beta Was this translation helpful? Give feedback.
-
|
Yes, discovery problem. But also a bit also has the issue that if the start of your repo's history is a very large import from another source, then the millions of lines of code that introduced will always drown out anything else the graph might ever show. It would be really useful to trim this down in a way that also affects the Y axis. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I like the suggestion to show contributions based on PRs. Some contributors put a bunch of commits in a single PR and others squash them into a single commit, so the PR counting feature would help compare them more fairly. |
Beta Was this translation helpful? Give feedback.
-
|
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.
-
|
You can select a date range by 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.
-
|
Further, in addition to filtering by "Additions", "Deletions", and "Commits", it would be nice to sort by "Additions minus Deletions" to compare contributors based on the total number of lines they've added to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I love the idea but this would be difficult to do accurately since codebases have a lot of boilerplate generated code. Something that could work is getting the total line count by contributor for a specific directory since most projects have the non-generated code inside a single directory (e.g. src). |
Beta Was this translation helpful? Give feedback.
-
I want the feature, although it could be inefficient to implement efficiently without lots of statistics about the dependency between the kind of hierarchies that can be expected in directory structure, and the estimation of language distribution. Too bad nobody has such data! |
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.
-
|
Thank you for contributing more than only opinions. |
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.
-
|
Yes, and a full list of all contributors (sometimes there are only top 100 contributors shown) |
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.
-
|
Seconded, currently using this to browse through FFmpeg's contributors and figure out how much of Fabrice Bellard's original contributions are still a part of the project, but this is currently not possible because he's presumably no longer in the top 100 contributors. https://stackoverflow.com/questions/74828879/how-much-of-modern-ffmpeg-is-written-by-fabrice-bellard |
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.
-
And especially if not; e.g., if I'm boasting to someone with screenshots from the contributions page, I want them maximally useful. |
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 could we do to make this data easier or better for you?
|
Beta Was this translation helpful? Give feedback.
-
How do you think this could be done, without relying even more heavily upon automated language detection? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I would love to have a contributors search option. Not sure if this is already being worked on or not. |
Beta Was this translation helpful? Give feedback.
-
|
A slightly unusual use case but I thought I share it with you. I'm one of the authors of the Thoughtworks technology radar, a publication with 200k+ readers. Thoughtworks is a medium-size global software consulting company, and we publish the tech radar twice a year, listing ~100 interesting technologies we've come across in each report. This is not market research, we ask our consultants what to include. In the process of deciding which of the proposed technologies will end up on a given volume of the radar, we usually consult the contributors page on Github (for open source software only, of course). Twice a year Other repositories Is the project still actively developed? How long has it been around for? Are there key contributors? How many? Which organisation are they affiliated with? As alluded to above, if we find that the software has been around for years and development activity is low / has decreased substantially year over year, we will likely not include it in our report. If it is very new with only one contributor we consider waiting for another six months before including it, to see whether it will make it to an at least somewhat stable state. It also affects how we classify the software. Works well as is (for our use case). I'm a user and maintainer of open source software, too. What I described above was only the use in the context of the Thoughtworks tech radar. |
Beta Was this translation helpful? Give feedback.
-
Occasionally.
In mine and others.
In mine repos: to remind of the role of a contributor. In other repos: to find out who are the main developers; how much others are contributing; deduce stage of the development.
I do this just to get better understanding of activity.
Date range might be helpful sometimes and just saw that you can do it. A corresponding note above the graph could be helpful. Removing the range to get "all time" could be nice too. Also sometimes list of contributors in the graphs doesn't match list in code browser (example), which looks like a bug.
Seems fine otherwise, please don't ruin it by redoing from scratch. |
Beta Was this translation helpful? Give feedback.
-
I'd like to be able to look at the entire org, not just one repo |
Beta Was this translation helpful? Give feedback.
-
|
Oh Lord, So I am just now beginning to learn Code. I think what you guys do on here is awesome. I am also new to GitHub so if there is a better place to request than I apologize. There are a number of items I would like to fund a team to solve for Cockatrice. Some easy ones such as changing the card database to pull the latest version of a card to adding in a voice chat function. My email is Mr.Tibbetts69@gmail.com. Feel free to shoot me an email if you're interested or point me towards those who might be. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
How often do you use these graphs? -- multiple times a week |
Beta Was this translation helpful? Give feedback.
-
|
This was almost exactly my feedback, but wanted to elaborate. I mostly use Insights to determine health of a candidate dependency before I adopt it. Top data points are:
It would be great if there was a Insights 'Risks' section which automated some of this analysis, highlighting if dependencies are out of date or have known vulnerabilities or are otherwise risky, issues / pull requests are being ignored, only one or two people contribute and/or have write access, risky transitive dependencies, project appears abandoned or in maintenance-only mode, little or no documentation, little or no community standards, etc. It could also act as a TODO list for repo maintainers to bring their packages up to production-worthy standards. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
About the requested feedback:
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
首页的贡献者显示错误 不刷新啊，缓存了多久 点进去没这个人 首页有这个人 |
Beta Was this translation helpful? Give feedback.
-
|
I use this both for my "own" repositories, and others. In the first case, I want to see how I compare to other contributors. It mainly works well for this case, but I think it focuses a bit too much on "commit count" and not "line count", since a few huge commits look like nothing, but a ton of one-line fixes shoots in the sky. Maybe have a toggle for plotting commit count vs line count? In the second case, I am trying to figure out who is the "active" or "driving" developer. That is a vague term, and it usually involves reviewing a lot of PRs, and contributing code, often, regularly and recently. The contributors page is a bit less helpful in this. For this, I would like to see some kind over overall gauge of developer engagement with the repo, i.e. including PRs opened/closed/reviewed/commented, bugs opened/closed/commented, and also as per above, not only the commit count but also the accumulated line count. And it would be nice if it was easy to visualize all this both on an "accumulated" aspect, everything that has happened since the repo started, to some kind of "latest", to see if someone used to do a lot but has now dropped out of the project. Kind of a "Fallen Heroes" ranking... |
Beta Was this translation helpful? Give feedback.
-
The info above duplicates another open discussion - #46661 |
Beta Was this translation helpful? Give feedback.
-
|
Yes I don't know |
Beta Was this translation helpful? Give feedback.
-
How much and in which ways different individuals are contributing to a repo.
For student repos, we can initiate discussions based on indicators from the contributions page. In general, study team dynamics and see if there are inbalances in the efforts of contributors where discussions can be helpful.
|
Beta Was this translation helpful? Give feedback.
-
|
👋 Thanks everyone! This was really useful feedback that's really going to help our planning ✨ |
Beta Was this translation helpful? Give feedback.
and others
-
Select Topic Area
Product Feedback
Body
👋 We'd love to know how you use the Contributors graphs on the Repository Insights tab (navigate to https://github.com/[REPO_NAME]/graphs/contributors), or click on "Insights" < "Contributors" from your repository.
Feedback we'd love to hear from you
Beta Was this translation helpful? Give feedback.
All reactions