Add "Hits" (Page View Counter) Badge to ALL @dwyl Repos/Projects so we can Chart Popularity Over Time
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 451
- Forks
- 63
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 1
Description
The "Hits" project two goals to:
a. collect data on view counts for our various projects/repositories so that we know how many people are viewing / reading them. (Sadly, most people don't star repos, even when they find them useful!)
b. serve as example project that complete beginners can use to learn Node.js and Elixir with a "real world" application/use-case.
Todo:
- Manually add Hits Badge to our most popular repositories:
Bonus Level
- write a script that adds a Hits "Badge" to a repository
readme.md. - and creates a Pull Request in the repo.
Note: We have deliberately not "publicised" the "Hits Service"
except for https://github.com/dwyl/repo-badges/tree/c2444c3a6d20d9f7fc381a471e7e20a8de8b94e9#github-repo-hit-counter-
and yet quite a few non-dwyl people/projects appear to be using it:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the repository README and the repo-badges example linked in the issue, then review the checklist for manually adding the Hits badge to repositories. Done means the relevant @dwyl projects have badges, with the bonus script updating a readme.md and creating a pull request for a repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100