git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: AMMAAAR BAKSHI <the.ammaar.ic@gmail.com>
To: git@vger.kernel.org
Subject: [RFC] New command: git-recall -- a developer standup/activity tool
Date: Mon, 13 Apr 2026 05:13:34 +0530	[thread overview]
Message-ID: <CACqkj0pxih1BSa8z9+Yw-g55G1rNcvvQao+SLwQ7B-eQodcvgg@mail.gmail.com> (raw)

Hi,

I'd like to propose a new command: `git recall`.

## Motivation

Developers often need a quick way to review what they (or their team)
committed recently -- for standups, weekly summaries, or general
self-review. Currently this requires constructing a `git log` invocation
with --author, --since, --oneline, and formatting flags, which is
non-obvious for casual users.

## Proposal

`git recall` would be a porcelain command that shows a formatted
summary of recent commits, grouped by date:

  git recall              # last 1 week (default)
  git recall --day        # last 1 day
  git recall --week -2    # last 2 weeks
  git recall --month      # last 1 month
  git recall --year       # last 1 year

Example output:

  --------------------------------------------------
    git recall  --  Last Week  (since 2026-04-06)
  --------------------------------------------------
    2026-04-11
    448e66e  Add login page  @ 19:41  Alice
    2026-04-10
    91bc3fa  Fix null pointer  @ 14:22  Bob
  --------------------------------------------------
    Total commits: 2
  --------------------------------------------------

## Implementation

I have a working standalone implementation in pure C with no
dependencies, available at:

  https://github.com/AMMAAR-IC/git-recall

It currently runs as an external binary (git-recall). I am interested
in contributing this as a built-in Git subcommand if the community
finds the idea worthwhile.

I am aware that similar output can be produced via:

  git log --oneline --since=1.week.ago --author=$(git config user.name)

However, git recall aims to provide a more discoverable, human-friendly
interface for this common workflow, similar to how `git switch` and
`git restore` were introduced to simplify `git checkout`.

## Questions for the community

1. Is this functionality considered within scope for a built-in command?
2. Would `git recall` be an appropriate name, or would something like
   `git activity` or `git standup` be preferred?
3. Are there existing plans or discussions around a similar feature?

I am happy to write a proper patch series if the idea is well-received.

Thank you for your time.

Ammaar Bakshi
https://github.com/AMMAAR-IC/git-recall


             reply	other threads:[~2026-04-12 23:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-12 23:43 AMMAAAR BAKSHI [this message]
2026-04-13 18:07 ` [RFC] New command: git-recall -- a developer standup/activity tool Tian Yuchen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACqkj0pxih1BSa8z9+Yw-g55G1rNcvvQao+SLwQ7B-eQodcvgg@mail.gmail.com \
    --to=the.ammaar.ic@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).