On 30/10/26 22:51, Lucien Gentis wrote:
Thanks Jason, great job ; things are much clearer yet !
Excellent, glad to hear it!
I’ll try this procedure, and come back here.
--- One suggestion : if more than one file is modified, instead of
committing each file one by one, what about using the -a option :
instead of :
|The -a option makes me nervous - I've had it add/commit things in the
past that I didn't want, so I thought explicit is better. This is
personal preference when using git though.|
--- One question : what is the purpose of creating a new branch ? (
|% git switch -c bind-fr-update|
||
||
Why not directly committing the changes with "git push" ?
This again comes down to agreement on the right process per repo,
really. Common sense usually prevails; if a commit is trivial, sure,
commit straight to "trunk", main or whatever the base branch is. If the
change is logically big enough, or you think it might need a pull
request (PR) and hence some discussion before merging, a branch-PR-merge
process is usual.
I don't think this has been decided for us as a group yet though.
