Many many people have difficulties getting involved in an existing Github project.
The most common mistake is cloning the repository they want to contribute to, DO NOT DO THAT!
First create a Fork of that repository, then clone that fork ...
The second biggest mistake is not creating a private branch, thus making changes to the 'Master' branch (In PcmHacks case it's called 'develop' ... ), DO NOT DO THAT!
Create your own branch, make your changes in that branch, commit them to that branch, then push that branch to your fork, then create a pull request from your fork.
The next mistake is miss understanding the Origin / Upstream naming, I must admit it is confusing, but not if you look at it right.
Your fork is Origin, it's the origin of your clone ... The repository that you forked, is Upstream of your fork!
Local clone -> Origin (Your fork) -> Upstream (The repository you forked).
You pull from upstream, you push to origin.
Simply stated steps ...
I am NOT A DOCUMENT WRITER, I do the best I can!Remote,
. . Fork a repository
Local,
. . Clone that fork local
. . Create the canonical name 'upstream' (it points to the repository you forked, origin points to your fork and is automatically created)
. . Create a local branch
. . . . Make your modifications
. . . . Stage the changes
. . . . Commit the changes
. . . . Push that branch to your fork
Remote,
. . Create a pull request from your fork ...
------
After it's accepted (if it is ) ...
Local,
. . Pull the upstream repository to update the local clone
. . Push the local clone to update the fork
. . Delete your Feature branch
Remote,
. . Delete your Feature branch
I abhor the Git GUI in Visual Studio ... I prefer using Git via CLI.
However I whipped up this in hopes it would help others Git involved ... Enjoy!
2022-01-11
2022-01-15 2022-02-07GitWithPcmHacks-v2.pdf
(899.17 KiB) Downloaded 11 times
FMI See,
I will keep this location Updated.Visual Studio Git GUI pain relief, click here: Git CLI in Visual Studio!
Rebasing from the Visual Studio Git GUI, click here: Confused Rebase in Visual Studio Git GUI!
Comments, Improvements, Corrections, Critiques welcome ...
As always, I am ALWAYS willing to help anyone ... To the point of sticking my nose in where it's not wanted sometimes!
But that's me, don't like it (or me), go suck an egg ...