git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/1] documentation: guide of best practices for GIT developer

From
Guillaume Cogoni <cogoni.guillaume@gmail.com>
Date
Apr 13, 2022, 16:36 UTC
Message-ID
<CAA0Qn1tZxGR0cUi2JSJtTFYe2Nk9xoGuHkruji1-53-Fhokmig@mail.gmail.com>
In-Reply-To
<CAJyCBOS=xCEmX3yPduDEQfkVYUUiawQ7sYgNHi2dGe-R2W5r-g@mail.gmail.com>

On Wed, Apr 13, 2022 at 4:36 PM Shaoxuan Yuan <shaoxuan.yuan02@gmail.com> wrote:

> Wouldn't there be a possibility that this doc can degrade into a list of
> personal taste?

Of course, it could end like this, if someone writes something in this document, it's because that person likes it. People are not going to recommend something they don't use. But, I also think that it's not really bad because the purpose it's to have a bunch of tools that might interest others.

> The tools that people use can vary in an incredible way, thus the workflow
> defined by multiple tools can go even further. I think a workflow here is highly
> opinionated, and such a thing may disturb newcomers?

Yup, you got a point, it's a bit complicated to recommend a workflow because there is a lot of variety. But, about tools, it's possible because you just say how this tool can be useful for the project. In my first recommendation I propose the built-in debugger of VS Code and say that "It can be used to isolate certain parts of code, with this you may be able to ask more precise questions when you are stuck.". I think that recommendation may not disturb newcomers or other Git developers because it's only a tip, use the tool or not, you have the choice.

> Wouldn't it be better to let people decide on their own tools and Git
> should stay respectful?

It's just a tool recommendation, and I don't force anyone to use it. Is it the name of the file "WorkingOnGit" that makes you think it's a mandatory thing? Maybe "HelpToolForGit" is better?

> Let alone most people come into the community as
> developer, if they are going to be "WorkingOnGit", so they may already be
> well-suited in their own workflow?

Yes, naturally, but even if people have their own workflow with this tool or this tool, maybe if you recommend a tool that is "better" for working on Git, will they change their habits? But, as I said it's just a recommendation, the final choice of whether to use it or not, is up to them.

Thanks, I appreciate your answer and I hope I've answered your questions. I think simply recommending tools is a good thing, because, as you mentioned, recommending a workflow is complicated.

SIncerely,
COGONI Guillaume
Previous: Shaoxuan YuanNext: COGONI Guillaume
Message 4 of 17 in “documentation: guide of best practices for GIT developer”
  1. 0/1 documentation: guide of best practices for GIT developerCOGONI Guillaume, Apr 12, 2022
  2. 1/1 documentation: guide of best practices for GIT developerCOGONI Guillaume, Apr 12, 2022
  3. Shaoxuan YuanApr 13, 2022
  4. Guillaume CogoniApr 13, 2022
  5. 0/1 Documentation/ToolsOnGit.txt: gather information about toolsCOGONI Guillaume, Apr 16, 2022
  6. 1/1 Documentation/ToolsOnGit.txt: gather information about toolsCOGONI Guillaume, Apr 16, 2022
  7. Matthieu MoyApr 16, 2022
  8. Philip OakleyApr 16, 2022
  9. Junio C HamanoApr 16, 2022
  10. 0/1 Documentation/ToolsForGit.txt: Tools for developing GitCOGONI Guillaume, Apr 17, 2022
  11. 1/1 Documentation/ToolsForGit.txt: Tools for developing GitCOGONI Guillaume, Apr 17, 2022
  12. Matthieu MoyApr 17, 2022
  13. 0/1 Documentation/ToolsForGit.txt: Tools for developing GitCOGONI Guillaume, Apr 20, 2022
  14. 1/1 Documentation/ToolsForGit.txt: Tools for developing GitCOGONI Guillaume, Apr 20, 2022
  15. Junio C HamanoApr 20, 2022
  16. 0/1 Documentation/ToolsForGit.txt: Tools for developing GitCOGONI Guillaume, Apr 21, 2022
  17. 1/1 Documentation/ToolsForGit.txt: Tools for developing GitCOGONI Guillaume, Apr 21, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.