Differences

This shows you the differences between two versions of the page.

--- git_github_workflow [2020/01/27 15:03] – [Making some local changes] rpjday
+++ git_github_workflow [2020/01/27 17:03] (current) – [Clone your personal fork to your local machine] rpjday
@@ Line 21: / Line 21: @@
 ==== Clone your personal fork to your local machine ====
-Once you've made that personal GitHub fork (agin, in my case, ''rpjday/libpod''), you need to make one more copy of the repository -- this one will be clone of your personal fork to your //local// machine, which represents the working tree in which you create new branches and make local changes that you'll push to your GitHub fork for eventual incorporation into the public project, but here's the trick for clarity.
+Once you've made that personal GitHub fork (agin, in my case, ''rpjday/libpod''), you need to make one more copy of the repository -- this one will be a clone of your personal fork to your //local// machine, which represents the working tree in which you create new branches and make local changes that you'll push to your GitHub fork for eventual incorporation into the public project, but here's the trick for clarity.
 Since you'll (shortly) be working with two remotes for this workflow, when you clone your personal fork, select a remote name other than the default of ''origin'' -- I'll use the remote name of ''rpjday'' to clearly identify that this is the remote corresponding to my personal fork over at GitHub, not the public project:
@@ Line 28: / Line 28: @@
 $ mkdir podman/libpod
 $ cd podman/libpod
-$ git clone https://github.com/rpjday/libpod git
+$ git clone -o rpjday https://github.com/rpjday/libpod git
 </code>
@@ Line 145: / Line 145: @@
 <code>
-$ git commit -a -m "silly changes to README.md"
+$ git commit -a -m "README.md: silly changes"
-[topic/rpjday/issue42 77fad5f] topic/rpjday/issue42
+[rpjday/README_changes b1a09348] README.md: silly changes
-file changed, 1 insertion(+), 1 deletion(-)
+file changed, 4 insertions(+)
 $
 </code>
 ==== Pushing your work ====
-At this point, you can push this new branch to your GitHub fork:
+You can continue adding and committing (related) work to this feature branch and, once you're satisfied, you can push that branch to your personal GitHub fork with:
 <code>
-$ git push rpjday/README_changes
+$ git push rpjday rpjday/README_changes
 </code>
 ==== And over At GitHub ====
-Provided you're logged into your account at GitHub, you'll suddenly see the appearance of a new branch ''sillyb''. If you think it's ready to go, you can select "Compare & pull request" to examine and confirm that you want to hand that off to the main project.
+Provided you're logged into your account at GitHub, you'll suddenly see the appearance of a new branch ''rpjday/README_changes''. If you think it's ready to go, you can select "Compare & pull request" to examine and confirm that you want to hand that off to the main project.
-If all goes well and your change is accepted and committed, you will have to perform the two earlier steps to fetch and merge your changes into your local clone into the ''master'' branch:
+If all goes well and your change is accepted and committed (in this case, into the ''master'' branch), you will have to perform the two earlier steps to fetch and merge your changes into your local clone into the ''master'' branch:
 <code>
-$ git fetch progit
+$ git fetch libpod
-$ git merge progit/master
+$ git merge libpod/master
 </code>
-In addition, you can now delete the ''sillyb'' branch if you have no further use for it.
+In addition, if you have no further need of that local feature, you can delete it:
+<code>
+$ git branch -d rpjday/README_changes
+</code>
+==== Adjusting your local branch ====
+Given the possibility that your pull request might provoke some comments about possible improvements, you can make those local improvements, stage them and commit them on the same branch as before, then force push that branch to replace the older one:
+<code>
+$ git push -f rpjday rpjday/README_changes
+</code>