-
Notifications
You must be signed in to change notification settings - Fork 21
Add 'Used by' section in README.md #61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
In those search results, I'm only seeing the Google/flatbuffers repo worth mentioning. Most of the other projects looked like school projects. |
Using badges might confuse people with a status of other projects, but I like the stars count. I also find it a little hard to read the white text on green background. Maybe something a bit more formal? Used ByIt would be nice if we could have a badge (like the stars count) that shows the total search results. |
I like your revision 👍 Yes, I tried, but I did not find something like this.
|
This issue got a little further recently, there is almost no similar tool for generating Used By quantities on the market, so I recently made one (in beta). It can automatically generate a 'Used By' badge, the number is fetched from the https://github.com/cpp-linter/cpp-linter-action/network/dependents page, and creates a pull request when the badge number changes with a GitHub Action. Here is the last Used By badge of cpp-linter-action for example: Just wanted to see if there were any thoughts or comments here. |
What's happening here? I see the link shows: Otherwise, that is a pretty cool idea! And I like the auto-PR feature. |
Oh, 465 users of package cpp-linter/cpp-linter-action + 58 users of package shenxianpeng/cpp-linter-action. So, 465 + 58 = 523. I'm ok with using that badge. You want to open a PR? |
Correct :) sorry for not mentioning it in my last comment. |
Since this PR #60 merged, this repo lost all the previous used by links (result is here), how about adding 'Used by' section in README.md? we could:
The text was updated successfully, but these errors were encountered: