{"thread":{"id":"65253","subject":"[GSOC 2026] Proposal Draft: Improving Git Advice Messages","startedAt":"2026-03-15T12:21:08Z","lastAt":"2026-03-15T12:46:23Z","messageCount":4,"participants":["Arsh Srivastava","Pushkar Singh"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"539029","messageId":"CAOAgETOX815iJcsZOjVSYXr+o-uSkkAkEJ3FE2xkt1ODBaOUmg@mail.gmail.com","threadId":"65253","inReplyTo":null,"subject":"[GSOC 2026] Proposal Draft: Improving Git Advice Messages","fromName":"Arsh Srivastava","fromEmail":"arshsrivastava00@gmail.com","sentAt":"2026-03-15T12:20:55Z","receivedAt":"2026-03-15T12:21:08Z","isPatch":false,"sender":{"key":"arshsrivastava00@gmail.com","avatar":"https://gravatar.com/avatar/31a57f3c18a3d49c0601d1863b1cea06242a5d6808b9bcc8fa8a801195d04cc7?d=mp&s=160"},"body":"I am Arsh and I recently completed my microproject submission\nrelated to improving advice messages when a branch switch fails\ndue to local changes.\n\nPatch discussion:\nhttps://github.com/git/git/pull/2233\n\nThrough this contribution, I became familiar with Git's advice\nsystem, the relevant code paths in unpack-trees.c, and the\nassociated tests. The review discussion also helped me\nunderstand the importance of keeping advice messages concise\nwhile guiding users toward safe workflows.\n\nBased on that experience, I am planning a GSoC proposal focused\non refining advice messages in several common scenarios across\nGit commands (such as checkout, push, merge, and rebase). So that\nI can preserve the user understanding while enhancing the UX.\n\nThe goal is not to introduce new mechanisms, but to improve\nclarity of existing advice messages, while not only\npreserving Git's preference for concise output and script-safe\nbehavior but also making the UI more user-friendly for the terminal\nusage.\n\nA rough draft of the proposal is attached below.\n\nI would greatly appreciate any feedback on whether this direction\nwould be useful.\n\nThank you for investing time in reading my draft and proposal.\n\nSigned off by: Arsh Srivastava \n"},{"id":"539030","messageId":"CALE2CrTWMcMOPoWH8HEN_Z8_H1tdhdN2a6hN9BkJ4xs=0DN3Xw@mail.gmail.com","threadId":"65253","inReplyTo":"CAOAgETOX815iJcsZOjVSYXr+o-uSkkAkEJ3FE2xkt1ODBaOUmg@mail.gmail.com","subject":"Re: [GSOC 2026] Proposal Draft: Improving Git Advice Messages","fromName":"Pushkar Singh","fromEmail":"pushkarkumarsingh1970@gmail.com","sentAt":"2026-03-15T12:31:21Z","receivedAt":"2026-03-15T12:31:33Z","isPatch":false,"sender":{"key":"pushkarkumarsingh1970@gmail.com","avatar":"https://avatars.githubusercontent.com/u/173247767?v=4"},"body":"Hi Arsh,\n\n> A rough draft of the proposal is attached below.\n>\n> I would greatly appreciate any feedback on whether this direction\n> would be useful.\n\nIt would be better to share the proposal in plain text on the mailing\nlist instead of attaching a PDF.\nThat makes it easier for reviewers to read inline and give feedback\ndirectly on specific parts.\n\nBest,\nPushkar\n"},{"id":"539031","messageId":"CAOAgETPhYra3XrevHptFu0x-se8D9ovRtgfomwFbhq9rSTXu6A@mail.gmail.com","threadId":"65253","inReplyTo":"CALE2CrTWMcMOPoWH8HEN_Z8_H1tdhdN2a6hN9BkJ4xs=0DN3Xw@mail.gmail.com","subject":"Re: [GSOC 2026] Proposal Draft: Improving Git Advice Messages","fromName":"Arsh Srivastava","fromEmail":"arshsrivastava00@gmail.com","sentAt":"2026-03-15T12:44:32Z","receivedAt":"2026-03-15T12:44:44Z","isPatch":false,"sender":{"key":"arshsrivastava00@gmail.com","avatar":"https://gravatar.com/avatar/31a57f3c18a3d49c0601d1863b1cea06242a5d6808b9bcc8fa8a801195d04cc7?d=mp&s=160"},"body":"Pushkar Singh writes:\n\n> It would be better to share the proposal in plain text\n> That makes it easier for reviewers to read inline and give feedback\n> directly on specific parts.\n\nThank you so much for the quick reply. The draft is as follows:-\n\nName and Contact Information:-\nPreferred Name: Arsh\nFull Name: Arsh Srivastava\nEmail: arshsrivastava00@gmail.com\nGitHub: https://github.com/arshsrivastava00\nMicro-Project Contribution: https://github.com/git/git/pull/2233\n\nTitle:-\nRefining Git Advice Messages for Common Error Scenarios\n\nSynopsis :-\nGit provides guidance through optional advice messages when\noperations fail or when repository states require user attention.\nWhile these hints are\ntechnically accurate, some messages assume familiarity with Git concepts and\nmay leave users unsure about the safest next step. This project\nproposes refining advice messages\nacross common Git commands such as checkout, push, merge, and rebase.\nThe goal is to improve clarity while preserving Git’s philosophy of\nconcise, script-friendly terminal output.\n\nBenefits to the Community:-\n- Improve Git’s usability by making advice messages easier to understand.\n- Help beginners recover from common errors more confidently and efficiently.\n- Maintain concise and safe workflows aligned with Git’s philosophy.\n- Improve consistency across Git commands so that they don’t look very long.\n- Contribute incremental improvements that can be easily reviewed and\nmerged upstream\n\nDeliverables:-\n- Audit existing advice messages across key Git commands.\n- Identify 12–15 scenarios where wording improvements could improve clarity.\n- Refine message wording without increasing verbosity.\n- Submit a patch series for each improvement.\n- Update related tests in the Git test suite.\n- Provide documentation updates where needed\n\nProposed Timeline:-\nWeeks 1–2: Review advice paths and finalize scenarios.\nWeeks 3–4: Improve checkout-related advice messages.\nWeeks 5–6: Improve push-related advice messages.\nWeeks 7–8: Refine merge and rebase advice.\nWeeks 9–10: Address remaining scenarios and ensure consistency.\nWeek 11: Documentation and cleanup.\nWeek 12: Address review feedback and finalize patch series.\n(if the timeline looks longer I considered Hofstadter's law and gave more space\nso that work is complete on time)\n\nRelated Work:-\nGit already includes an advice system implemented primarily in advice.c and\ncontrolled through configuration options such as advice.*.\nPrevious work in the Git project has focused on improving command\nconsistency and repository integrity checks. This project builds on the\nexisting advice infrastructure and focuses on refining message wording\nrather than introducing new mechanisms which would have complicated the\ncurrent git advice system even more.\n\nBiographical Information:-\nI am Arsh Srivastava. I am a developer interested in open-source systems and\ndeveloper tools. I have also mentored in SWoC and worked on many more open\nsource projects such as google-deepmind and opencv. I am currently in my 3 year\nof college where I am studying and I have always been curious and am known for\ngood communication skills and for a creative mind.\n\nOn Sun, 15 Mar 2026 at 18:01, Pushkar Singh\n wrote:\n>\n> Hi Arsh,\n>\n> > A rough draft of the proposal is attached below.\n> >\n> > I would greatly appreciate any feedback on whether this direction\n> > would be useful.\n>\n> It would be better to share the proposal in plain text on the mailing\n> list instead of attaching a PDF.\n> That makes it easier for reviewers to read inline and give feedback\n> directly on specific parts.\n>\n> Best,\n> Pushkar\n"},{"id":"539032","messageId":"CAOAgETPzGiYem3Z3rV5duhs07g=0A+-MO6bCi9MFARwrQPR7Aw@mail.gmail.com","threadId":"65253","inReplyTo":"CALE2CrTWMcMOPoWH8HEN_Z8_H1tdhdN2a6hN9BkJ4xs=0DN3Xw@mail.gmail.com","subject":"Re: [GSOC 2026] Proposal Draft: Improving Git Advice Messages","fromName":"Arsh Srivastava","fromEmail":"arshsrivastava00@gmail.com","sentAt":"2026-03-15T12:46:11Z","receivedAt":"2026-03-15T12:46:23Z","isPatch":false,"sender":{"key":"arshsrivastava00@gmail.com","avatar":"https://gravatar.com/avatar/31a57f3c18a3d49c0601d1863b1cea06242a5d6808b9bcc8fa8a801195d04cc7?d=mp&s=160"},"body":"Pushkar Singh writes:\n\n> It would be better to share the proposal in plain text\n> That makes it easier for reviewers to read inline and give feedback\n> directly on specific parts.\n\nThank you so much for the quick reply. The draft is as follows:-\n\nName and Contact Information:-\nPreferred Name: Arsh\nFull Name: Arsh Srivastava\nEmail: arshsrivastava00@gmail.com\nGitHub: https://github.com/arshsrivastava00\nMicro-Project Contribution: https://github.com/git/git/pull/2233\n\nTitle:-\nRefining Git Advice Messages for Common Error Scenarios\n\nSynopsis :-\nGit provides guidance through optional advice messages when\noperations fail or when repository states require user attention.\nWhile these hints are\ntechnically accurate, some messages assume familiarity with Git concepts and\nmay leave users unsure about the safest next step. This project\nproposes refining advice messages\nacross common Git commands such as checkout, push, merge, and rebase.\nThe goal is to improve clarity while preserving Git’s philosophy of\nconcise, script-friendly terminal output.\n\nBenefits to the Community:-\n- Improve Git’s usability by making advice messages easier to understand.\n- Help beginners recover from common errors more confidently and efficiently.\n- Maintain concise and safe workflows aligned with Git’s philosophy.\n- Improve consistency across Git commands so that they don’t look very long.\n- Contribute incremental improvements that can be easily reviewed and\nmerged upstream\n\nDeliverables:-\n- Audit existing advice messages across key Git commands.\n- Identify 12–15 scenarios where wording improvements could improve clarity.\n- Refine message wording without increasing verbosity.\n- Submit a patch series for each improvement.\n- Update related tests in the Git test suite.\n- Provide documentation updates where needed\n\nProposed Timeline:-\nWeeks 1–2: Review advice paths and finalize scenarios.\nWeeks 3–4: Improve checkout-related advice messages.\nWeeks 5–6: Improve push-related advice messages.\nWeeks 7–8: Refine merge and rebase advice.\nWeeks 9–10: Address remaining scenarios and ensure consistency.\nWeek 11: Documentation and cleanup.\nWeek 12: Address review feedback and finalize patch series.\n(if the timeline looks longer I considered Hofstadter's law and gave more space\nso that work is complete on time)\n\nRelated Work:-\nGit already includes an advice system implemented primarily in advice.c and\ncontrolled through configuration options such as advice.*.\nPrevious work in the Git project has focused on improving command\nconsistency and repository integrity checks. This project builds on the\nexisting advice infrastructure and focuses on refining message wording\nrather than introducing new mechanisms which would have complicated the\ncurrent git advice system even more.\n\nBiographical Information:-\nI am Arsh Srivastava. I am a developer interested in open-source systems and\ndeveloper tools. I have also mentored in SWoC and worked on many more open\nsource projects such as google-deepmind and opencv. I am currently in my 3 year\nof college where I am studying B.Tech CSE with minors in AI/ML and I\nhave always been\ncurious and am known for good communication skills and for a creative mind.\n\nOn Sun, 15 Mar 2026 at 18:01, Pushkar Singh\n wrote:\n>\n> Hi Arsh,\n>\n> > A rough draft of the proposal is attached below.\n> >\n> > I would greatly appreciate any feedback on whether this direction\n> > would be useful.\n>\n> It would be better to share the proposal in plain text on the mailing\n> list instead of attaching a PDF.\n> That makes it easier for reviewers to read inline and give feedback\n> directly on specific parts.\n>\n> Best,\n> Pushkar\n"}]}