Login

u/Fit_Mechanic_815

▲ 1 r/WebApps

Do you still write weekly dev reports manually?

I’ve been thinking about how teams handle reporting from Git activity.

In most places I’ve worked or seen, people still write weekly updates manually, even though the data already exists in commits, PRs, and merges.

We tried a different approach recently: generating summaries directly from Git activity (basically turning commits into readable updates like “what shipped”, “what’s in progress”, etc.).

It works surprisingly well when commit messages are decent, but can get noisy otherwise.

I’m curious how others handle this:

•	Do you write reports manually?

•	Use dashboards (GitHub/GitLab)?

•	Or automate it somehow?

Also wondering:👉 do you actually find these reports useful, or are they just a formality?

Would be interesting to hear real workflows, especially in small teams vs larger ones.

reddit.com
u/Fit_Mechanic_815 — 1 day ago
▲ 1 r/roastmystartup

Do you still write weekly dev reports manually?

I’ve been thinking about how teams handle reporting from Git activity.

In most places I’ve worked or seen, people still write weekly updates manually, even though the data already exists in commits, PRs, and merges.

We tried a different approach recently: generating summaries directly from Git activity (basically turning commits into readable updates like “what shipped”, “what’s in progress”, etc.).

It works surprisingly well when commit messages are decent, but can get noisy otherwise.

I’m curious how others handle this:

  • Do you write reports manually?
  • Use dashboards (GitHub/GitLab)?
  • Or automate it somehow?

Also wondering:
👉 do you actually find these reports useful, or are they just a formality?

Would be interesting to hear real workflows, especially in small teams vs larger ones.

reddit.com
u/Fit_Mechanic_815 — 1 day ago
▲ 2 r/git+1 crossposts

Using Git activity to generate a weekly newsletter automatically

Most engineering teams already have all their activity in Git:

  • commits
  • pull requests
  • merges

But when it comes to sharing updates (with the team, stakeholders, or even users), it usually turns into a manual newsletter or status report.

So instead of writing those updates manually, this approach turns Git activity into a daily + weekly newsletter automatically → https://gitmore.io

The idea is pretty straightforward:

  • analyze repo activity over the week
  • structure it into something readable
  • send it as a clean summary

Instead of raw logs, the newsletter highlights things like:

  • what shipped
  • what’s still in progress
  • notable changes

What’s interesting is that it’s not just for devs, it’s actually readable by non-technical people too. So it can double as:

  • internal team updates
  • stakeholder reports
  • lightweight product updates

No one has to ask “what happened this week?” or write it manually anymore.

Curious how others handle this:

  • Do you send weekly updates/newsletters?
  • Is it manual or automated?
  • Who usually writes it?

Feels like this is one of those small things that quietly eats time every week.

u/Fit_Mechanic_815 — 3 days ago