Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Do we have an idea of how many people read Git Rev News?

Open
#808 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
analytics

Research direction

Start by identifying how Git Rev News pages and the email edition are currently published at https://git.github.io/; no files or tests are named. Define what page-view, subscriber, trend, and audience data can be collected, and document a repeatable report if the project can support it.

Written by the indexing model from the issue text.

Description

I think it could be interesting to have an estimate of how many people, and if possible too what kind of people, read Git Rev News each month, for a number of reasons:

  • The trend over the months and years could be some kind of long term feedback.
  • If we see that some months more people read it, maybe it could give an idea about which kind of content is preferred.
  • If it looks like people reading it could be interested in participating in Git development, maybe we could add content to help them or encourage them.
  • If it looks like people reading it could be interested in participating in Git Rev News, maybe we could take advantage of that too.

So can we have a an idea of the number of views of the different pages on https://git.github.io/? Can we have the number of subscribers to the email edition of the newsletter?

@jnareb, @mjaix, @sivaraam, @stepnem what do you think about this?

Dominant language
CSS
Stars
373
Forks
325
Avg merge
4d 18h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from git/git.github.io

All issues in git/git.github.io

Similar issues

More Data Visualization issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.