You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this issue is not directly related to the counter but neverless it draws the counter as unreliable because summons additional hits per each forked readme.md.
The root of the issue is that when the repository with the readme and counter inside is forked then the hardcoded url with the original user is left as is. So the forked page will increment the same counter.
As an additional plus there would not be counted any click from the repo owner and the counter will be stored in a repository.
The minus is that the github does not increment a profile repo page views counter on a profile page view, where: github.com/user/user - profile repo page, github.com/user - profile page.
The text was updated successfully, but these errors were encountered:
I know this issue is not directly related to the counter but neverless it draws the counter as unreliable because summons additional hits per each forked readme.md.
The root of the issue is that when the repository with the readme and counter inside is forked then the hardcoded url with the original user is left as is. So the forked page will increment the same counter.
The issue has already mentioned many years ago and there is still not fixed:
https://stackoverflow.com/questions/32408146/does-github-support-username-variable-in-readme-md
The alternative implementation is to accumulate a repo github view hits using github actions and reference it by json data badge:
https://github.com/andry81/github-accum-stats
As an additional plus there would not be counted any click from the repo owner and the counter will be stored in a repository.
The minus is that the github does not increment a profile repo page views counter on a profile page view, where:
github.com/user/user
- profile repo page,github.com/user
- profile page.The text was updated successfully, but these errors were encountered: