Awesome-go: A copy of this list with number of stars/forks/issues provided
Hi, I made a script to scrape this awesome list and augment each repository item with its stats, namely number of stars, forks and open issues.
Here is the link to augmented README.md.
I do agree with the comments in the previous discussions that number of stars/forks do not indicate the quality or usefulness of repos very well. Number of open issues on the other hand can tell a lot.
Anyways, it helped me to navigate through the list.
kaxap
All 21 comments
Nice, @kaxap!
UPD: https://github.com/kaxap/awesome-go-processed/issues/1, https://github.com/kaxap/awesome-go-processed/issues/2
kamilsk
on 11 May 2018
@kamilsk Thanks!
Added last update as well.
kaxap
on 12 May 2018
I would prefer to see this next to main README and no added to it. There could be link to it on top of README.
matrixik
on 9 Jul 2018
I would prefer to see this on site (awesome-go.com) not on README, build site on:
- merged on master (as it is today)
- automatic 0am (crontab by example)
On README polluted (visually)
avelino
on 9 Jul 2018
I created something similar which is already integrated with the old build system: commit diff
But if you start the docker container now you need to provide the -e GH_TOKEN=<ghtoken> where <ghtoken> is generated here.
You need the token because of the GitHub API Ratelimiting.
It looks like this right now but of course we can change the CSS:
A compiled version on my page
Ma124
on 22 Jan 2019
@avelino @kaxap What do you think about this?
Ma124
on 23 Jan 2019
@Ma124 I think it's a great idea! Personally, I had issues with the markdown's layout since I had added too many new columns. In this case I am sure @avelino can check your CSS modifications as well.
kaxap
on 24 Jan 2019
@kaxap I'm planning on making the tables sortable, adding octicons after the numbers in the columns (star, fork etc) and to provide a button to hide individual columns
Ma124
on 24 Jan 2019
@avelino @kaxap
I added sorting and icons
Is this better?
Ma124
on 26 Jan 2019
@Ma124 yeah, definitely. Looks redundant on a short table but long table absolutely needs this, imho.
kaxap
on 2 Feb 2019
@rororofff has funded $20.00 to this issue.
- Submit pull request via IssueHunt to receive this reward.
- Want to contribute? Chip in to this issue via IssueHunt.
- Checkout the IssueHunt Issue Explorer to see more funded issues.
- Need help from developers? Add your repository on IssueHunt to raise funds.
IssueHuntBot
on 26 Mar 2019
@rororofff I'm still working on it. I've made Awesome Framework
Ma124
on 26 Mar 2019
2445
Ma124
on 26 Mar 2019
2445
That way we don't have indexing on Google, read more: #983
avelino
on 26 Mar 2019
Why that? Isn't the result on awesome-go.com the same?
Ma124
on 27 Mar 2019
Why that? Isn't the result on awesome-go.com the same?
People usually search for some library Go on Google, have the content in render (HTML) makes Google find the awesome-go.com
avelino
on 27 Mar 2019
I'm really sorry but I still don't get it. How could you solve that?
Ma124
on 27 Mar 2019
@avelino
I've read #983 several times now and the only SEO requirement you describe is that the file is put in the gh-pages branch and my pull request does that: https://github.com/Ma124/awesome-go-fork/tree/gh-pages .
Sorry if I'm annoying but I'm still not sure what the problem is so I can't fix it.
Ma124
on 18 Apr 2019
@avelino I wanted to re-ping this issue as the changes still would be useful, and could help with a lot of the other open issues.
Worth mentioning is that my proposal does render everything to a static file on gh-pages and therefore should not impact SEO ratings.
The sorting is done on the client-side instead. The program pulls the statistics, if triggered manually on Travis CI or automatically on every commit, and writes them to the static HTML file. These processes are handled by the Awesome-Framework which has an A+ Go Report Card () and a high unit test coverage (
)
You can try it out on my site.
These changes would help with #1446 and #2649 because you could, for example, sort by decreasing time since the last commit and find the projects that aren't maintained anymore more comfortably. It would also be trivial to add links to the GoReportCard and GoDoc.
The extraction of information from the markdown document could aid with #1548, too.
Ma124
on 20 Apr 2020
Hey @Ma124, this being in html rendering I find valid (as discussed here #3163 https://github.com/avelino/awesome-go/pull/3154#issuecomment-655652053, but not in the readme/github render), can you assume this implementation along with this issue?
avelino
on 13 Jul 2020
@avelino yes, I'd be very happy to do so.
Ma124
on 13 Jul 2020
Related issues
kevinburke
路
9Comments
flimzy
路
17Comments
xhit
路
6Comments
ldemailly
路
9Comments
PotHix
路
8Comments
Most helpful comment
@avelino I wanted to re-ping this issue as the changes still would be useful, and could help with a lot of the other open issues.
Worth mentioning is that my proposal does render everything to a static file on
) and a high unit test coverage (
)
gh-pagesand therefore should not impact SEO ratings.The sorting is done on the client-side instead. The program pulls the statistics, if triggered manually on Travis CI or automatically on every commit, and writes them to the static HTML file. These processes are handled by the Awesome-Framework which has an A+ Go Report Card (
You can try it out on my site.
These changes would help with #1446 and #2649 because you could, for example, sort by decreasing time since the last commit and find the projects that aren't maintained anymore more comfortably. It would also be trivial to add links to the GoReportCard and GoDoc.
The extraction of information from the markdown document could aid with #1548, too.