{"thread":{"id":"65471","subject":"[RFC] New command: git-recall -- a developer standup/activity tool","startedAt":"2026-04-12T23:45:09Z","lastAt":"2026-04-13T18:07:29Z","messageCount":2,"participants":["AMMAAAR BAKSHI","Tian Yuchen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"541448","messageId":"CACqkj0pxih1BSa8z9+Yw-g55G1rNcvvQao+SLwQ7B-eQodcvgg@mail.gmail.com","threadId":"65471","inReplyTo":null,"subject":"[RFC] New command: git-recall -- a developer standup/activity tool","fromName":"AMMAAAR BAKSHI","fromEmail":"the.ammaar.ic@gmail.com","sentAt":"2026-04-12T23:43:34Z","receivedAt":"2026-04-12T23:45:09Z","isPatch":false,"body":"Hi,\n\nI'd like to propose a new command: `git recall`.\n\n## Motivation\n\nDevelopers often need a quick way to review what they (or their team)\ncommitted recently -- for standups, weekly summaries, or general\nself-review. Currently this requires constructing a `git log` invocation\nwith --author, --since, --oneline, and formatting flags, which is\nnon-obvious for casual users.\n\n## Proposal\n\n`git recall` would be a porcelain command that shows a formatted\nsummary of recent commits, grouped by date:\n\n  git recall              # last 1 week (default)\n  git recall --day        # last 1 day\n  git recall --week -2    # last 2 weeks\n  git recall --month      # last 1 month\n  git recall --year       # last 1 year\n\nExample output:\n\n  --------------------------------------------------\n    git recall  --  Last Week  (since 2026-04-06)\n  --------------------------------------------------\n    2026-04-11\n    448e66e  Add login page  @ 19:41  Alice\n    2026-04-10\n    91bc3fa  Fix null pointer  @ 14:22  Bob\n  --------------------------------------------------\n    Total commits: 2\n  --------------------------------------------------\n\n## Implementation\n\nI have a working standalone implementation in pure C with no\ndependencies, available at:\n\n  https://github.com/AMMAAR-IC/git-recall\n\nIt currently runs as an external binary (git-recall). I am interested\nin contributing this as a built-in Git subcommand if the community\nfinds the idea worthwhile.\n\nI am aware that similar output can be produced via:\n\n  git log --oneline --since=1.week.ago --author=$(git config user.name)\n\nHowever, git recall aims to provide a more discoverable, human-friendly\ninterface for this common workflow, similar to how `git switch` and\n`git restore` were introduced to simplify `git checkout`.\n\n## Questions for the community\n\n1. Is this functionality considered within scope for a built-in command?\n2. Would `git recall` be an appropriate name, or would something like\n   `git activity` or `git standup` be preferred?\n3. Are there existing plans or discussions around a similar feature?\n\nI am happy to write a proper patch series if the idea is well-received.\n\nThank you for your time.\n\nAmmaar Bakshi\nhttps://github.com/AMMAAR-IC/git-recall\n"},{"id":"541494","messageId":"31c50eb0-0fc0-46fb-a277-b5fbb28d1d9a@malon.dev","threadId":"65471","inReplyTo":"CACqkj0pxih1BSa8z9+Yw-g55G1rNcvvQao+SLwQ7B-eQodcvgg@mail.gmail.com","subject":"Re: [RFC] New command: git-recall -- a developer standup/activity tool","fromName":"Tian Yuchen","fromEmail":"cat@malon.dev","sentAt":"2026-04-13T18:07:16Z","receivedAt":"2026-04-13T18:07:29Z","isPatch":false,"body":"Hi Amar,\n\nOn 4/13/26 07:43, AMMAAAR BAKSHI wrote:\n> Hi,\n> \n> I'd like to propose a new command: `git recall`.\n> \n> ## Motivation\n> \n> Developers often need a quick way to review what they (or their team)\n> committed recently -- for standups, weekly summaries, or general\n> self-review. \n\nStandups, weekly summaries or general self-review...? These feel more \nlike workflow conveniences — is a built-in command really the right \nplace for them?\n\n\n> Currently this requires constructing a `git log` invocation\n> with --author, --since, --oneline, and formatting flags, which is\n> non-obvious for casual users.\n\nAdding a line like 'standup = log --since=yesterday --author=...' in \n'.gitconfig' is another nice way of achieving this ;-)\n\n> \n> ## Proposal\n> \n> `git recall` would be a porcelain command that shows a formatted\n> summary of recent commits, grouped by date:\n> \n>    git recall              # last 1 week (default)\n>    git recall --day        # last 1 day\n>    git recall --week -2    # last 2 weeks\n>    git recall --month      # last 1 month\n>    git recall --year       # last 1 year\n> \n> Example output:\n> \n>    --------------------------------------------------\n>      git recall  --  Last Week  (since 2026-04-06)\n>    --------------------------------------------------\n>      2026-04-11\n>      448e66e  Add login page  @ 19:41  Alice\n>      2026-04-10\n>      91bc3fa  Fix null pointer  @ 14:22  Bob\n>    --------------------------------------------------\n>      Total commits: 2\n>    --------------------------------------------------\n> \n> ## Implementation\n> \n> I have a working standalone implementation in pure C with no\n> dependencies, available at:\n> \n>    https://github.com/AMMAAR-IC/git-recall\n> \n\nGood to hear that;\n\n> It currently runs as an external binary (git-recall). I am interested\n> in contributing this as a built-in Git subcommand if the community\n> finds the idea worthwhile.\n> \n> I am aware that similar output can be produced via:\n> \n>    git log --oneline --since=1.week.ago --author=$(git config user.name)\n> \n> However, git recall aims to provide a more discoverable, human-friendly\n> interface for this common workflow, similar to how `git switch` and\n> `git restore` were introduced to simplify `git checkout`.\n\nI suppose the 'checkout' command was split up and simplified because its \nmeaning isn’t particularly intuitive for ordinary users, is it? 'git \nlog', on the other hand, is, in my view, a very clear and \nstraightforward read-only command.\n\nYou said this is a more discoverable and human-fridenly interface. If \nthat’s the case, I think we should compare the merits of this method \nwith defining aliases directly in .gitconfig.\n\n> \n> ## Questions for the community\n> \n> 1. Is this functionality considered within scope for a built-in command?\n\nI don’t think it should be a built-in command.\n\n> 2. Would `git recall` be an appropriate name, or would something like\n>     `git activity` or `git standup` be preferred?\n\nTo be honest, the name 'recall' is a bit odd.\n\nAccording to dictionary.cambridge.org, 'recall' has at least two \nmeanings. I think this is your intention:\n\n\"...to bring the memory of a past event into your mind, and often to \ngive a description of what you remember...\"\n\nHowever,\n\n\"...to order the return of a person who belongs to an organization or of \nproducts made by a company...\"\n\nis another valid meaning. We say \"recall an email\" \"recall defective \nproducts\". This suggests that the word carries a connotation of \namendment/revocation. However, based on your description, this is a \n*read-only* operation, right?\n\nIf a \"casual user\" sees this command name, might he think: \"This is a \nlogging command, but why is it called 'recall'? Will it alter my commit \nhistory? Could there be other side effects?\" This is something we need \nto think about.\n\n> 3. Are there existing plans or discussions around a similar feature?\n> \n> I am happy to write a proper patch series if the idea is well-received.\n> \n> Thank you for your time.\n> \n> Ammaar Bakshi\n> https://github.com/AMMAAR-IC/git-recall\n\nThanks, Yuchen\n\n"}]}