Sounds like a great idea. Here it is from a repository owner perspective.
Though this may be a good reference.
I spent the weekend reading the gitub cli manual, in its entirety. Quite a
read and very informative.
GitHub Cli manual
https://cli.github.com/manual/
*****
This is the workflow I did just tis morning for a pull request, that a
collorabator did on my repo. Very thankfull.....
gh pr list
gh pr checkout 4 -b youtube
git diff main > temp.txt
**** Reviewed changes
notepad.exe temp.txt
*** Saw no problems so I did the next
git checkout main
git merge youtube
git push
verified pr was closed
gh pr list
No open Pull Requests, so closed.
Then I commented on issue and thanked the contributor.
gh issue comment 1 "Loooks good. Will incorporate today. Thank You."
I read the other article this morning and you can use browser in combination
with git, without githubcli.
Lewis Wood
lewislwood@xxxxxxxxx <mailto:lewislwood@xxxxxxxxx>
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> On
Behalf Of Jim Homme
Sent: Monday, November 7, 2022 7:56 AM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Git Article Outlining Typical Git Workflow
Hi,
This is a nice article that illustrates the common Git workflow from
starting to contribute to a project to creating your first pull request to
add changes to the original project. I'm going to make a cheat sheet from it
and add to it as I learn new things to do.
https://www.digitalocean.com/community/tutorials/how-to-create-a-pull-reques
t-on-github
Thanks.
Jim
==========
Jim Homme
Senior Digital Accessibility Consultant
Bender Consulting Services
412-787-8567
https://www.benderconsult.com/
Support the dreams of independence through employment for students with
disabilities with your Amazon purchases.
https://smile.amazon.com/ch/83-0988251
