On 12/18/19 6:54 AM, Brian (bex) Exelbierd wrote:
I have an alternative approach that I like that I feel like makes it
easier to keep the fork in sync. This feels like a huge point of
friction for new users and this is hte only reason I am proposing it.
1. Go to Pagure to the docs repo and get the clone URL (this may be an
https url and that is OK)
2. On your system clone this url: `git clone <docs repo clone url> -o
upstream`
This will create the repo as a remote called upstream. This is
mostly a detail and can be glossed over
3. Fork the repo in the Pagure UI
4. Copy your fork clone url (git@...)
5. `cd <repo directory>
6. `git remote add origin <fork clone url>`
At this point the master branch is linked to "upstream" and the fork is
origin. What this means is that, following hte rest of the directions,
keeping the repo in sync is as simple as `git checkout master; git pull`
+1 to this tip! That's a clever trick to get master linked to a
different remote from other branches. It also makes feature branching
easier to understand when things are set up this way.
Today I learned :)
--
Cheers,
Justin W. Flory
justinwflory.com
TZ=America/New_York
Pronouns: he/him/his