Difference between revisions of "Talk:Setup for Pull Requests"
From GnuCash
(2 Notes) |
|||
Line 23: | Line 23: | ||
The user should then be able to export the set variable and run the script, but I did'nt test it. | The user should then be able to export the set variable and run the script, but I did'nt test it. | ||
--[[User:Fell|Fell]] ([[User talk:Fell|talk]]) 20:01, 29 January 2018 (UTC) | --[[User:Fell|Fell]] ([[User talk:Fell|talk]]) 20:01, 29 January 2018 (UTC) | ||
+ | |||
+ | -- Sunfish62 reply -- | ||
+ | Frank, the text and formatting were taken directly from the original "Git for Newbies" (now "An Introduction to Git") page. In other words, I didn't create it--I just copied it. |
Revision as of 15:49, 4 February 2018
Origin vs. Upstream
I would have choosen the names the way:
- origin
- the original program/doc
- upstream
- my publications
- pull origin; push upstream sounds more logic to me.
Brackets
Until now we used <Replace this by your text> and [you might omit this] For your examples you should consider <syntaxhighlight lang="sh"> mkdir ~/github cd ~/github git clone git@github.com:"$YOUR-GITHUB-USERNAME"/gnucash.git </syntaxhighlight> resulting in:
mkdir ~/github
cd ~/github
git clone git@github.com:"$YOUR-GITHUB-USERNAME"/gnucash.git
The user should then be able to export the set variable and run the script, but I did'nt test it. --Fell (talk) 20:01, 29 January 2018 (UTC)
-- Sunfish62 reply -- Frank, the text and formatting were taken directly from the original "Git for Newbies" (now "An Introduction to Git") page. In other words, I didn't create it--I just copied it.