Re: ACTION 2023-02-07-a: Steven to make Pull Request for Unicode test

Git “novice’s guide”. Page one: “git is easy to understand once you view it as a multi-nodal time-independent stream of intertwined repositories which can be recombined in arbitrary combinations. So now you understand that, let’s…”


Getting started with GIT
Page 1: Set your username.
Page 2: 
"Caching your GitHub credentials in Git
If you're cloning GitHub repositories using HTTPS, we recommend you use GitHub CLI or Git Credential Manager (GCM) to remember your credentials.
Tip: If you clone GitHub repositories using SSH, then you can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "Generating an SSH Key."
GitHub CLI will automatically store your Git credentials for you when you choose HTTPS as your preferred protocol for Git operations and answer "yes" to the prompt asking if you would like to authenticate to Git with your GitHub credentials."



It's a perpetual problem with open source (which in general I love). People who write code seldom understand what people need to know.


"There's a closely related issue, however that I don't know how to solve yet without a big player with a lot of money, which is doing systematic user interface end user testing. We're not very good at that yet, we need to find a way to be good at it."
Eric Raymond, Why Open Source will Rule

Steven

On Tuesday 13 June 2023 15:08:27 (+02:00), C. M. Sperberg-McQueen wrote:

> 
> Norm Tovey-Walsh  writes:
> 
> >> Honestly, every time I use git, I hate it more.
> >
> > It’s a sharp tool, but a very useful one.
> 
> Like Steven, I found my first experiences with git painful and
> frustrating.  Tom Hillman recommended a GUI interface for git
> (unfortunately, I cannot remember what it was called), which helped me a
> great deal.  When I moved from the Mac to my current Linux box, I
> shifted to MaGit, which is convenient for emacs users.
> 
> Of course, part of what makes git painful for occasional users is the
> huge number of options on every interaction, and the huge number of
> situations which the documentation must describe and which make no sense
> to someone who does not use git in ways that lead to those situations.
> It's like reading discussions of bidding strategies in bridge, when you
> have never played bridge before.
> 
> So, for what it's worth, my advice is:
> 
> 1 Choose and use a (gui) interface for your environment.  I recommend
> one which exposes the underlying git commands it's executing.
> 
> 2 Take notes on the actions needed for the git usage patterns of the
> project(s) you're working in.
> 
> If anyone would find it helpful, maybe I should take an action to take
> my own notes on how to interact with the ixml repository and turn them
> into prose.
> 
> Michael
>

Received on Tuesday, 13 June 2023 20:26:15 UTC