star&fork count use githubbadges

[llitfkitfk]

[mingrammer]

it is too small to see at all ..

[mingrammer]

Hm, A little bit hard to read at least for me. Are there reasons to use the badges?

[llitfkitfk]

for auto-update

[mingrammer]

As we have an auto update script and I think that it is not very important that the stars & forks should be updated in realtime.

And it is a little bit hard to read because it's small size.

[llitfkitfk]

yes, I try to fix the small size svg issue. But markdown table format not allowed

[llitfkitfk]

@mingrammer fixed size issue

[mingrammer]

Yes, I see.

As I don't know, It is possible to use badges for open Issues?

The open issue column was added by mattn : https://github.com/mingrammer/go-web-framework-stars/pull/10

[llitfkitfk]

add open issue

[mingrammer]

I checked it.

But in this time, I think that there could be a problem. The beego and gin has difference of about 600 stars. (about 12200 and 11600) But the badges tell as if both have same number of stars. (12k)

How do you think about this?

[llitfkitfk]

wait for https://github.com/badges/shields/issues/999 ?

[stzminjae]

Yes, we should use that raw count instead of short for this repository

[llitfkitfk]

How about using githubbadges for stars/forks and shields for issue?

If shields support raw star and forks full count in the future, re-update then.

Any thought?

[mingrammer]

I want to keep consistency so that they have same format.

Using the shields only for issue count, the README could be not clean I think.

[mingrammer]

But, does Githubbadges means githubbadges.com ?

[llitfkitfk]

Yes

[stzminjae]

That's ok. I see that it shows full count.

The last issue could be there. It's README has about 30 web frameworks. So, it should requests the badges almost 90 times. It is too many and could causes slow rendering the count.

So .. ?