Post "Manage fork repository locally and remotely" article

[ZynoXelek]

This article aims to explain how to :

• Create a fork
• Work with a fork
• Pull request on the original repository

[ctmbl]

Great draft really!! Of course, I know, it's a draft 🙂

some temporary comments (more to my future self than you) until I find some time to continue your wonderful job:

• [x] git add before git commit (might be interesting to put some git status or/and git log --all --graph --oneline --decorate)
• [x] add a link to GitHub - Create a SSH key and GitHub - add a new SSH key when introducing clone-ning and pushing
• [x] it's far better to pull request before finishing your code (at the end of the first session for example) than waiting for the end of the development/writing of a feature, I'll never say it enough I guess 🥲
• [x] at the end to update your local fork -> to update your local copy: strictly speaking we don't know if you cloned a fork or not, when speaking about cloned repositories we don't use such naming
• [x] some typos:
  • now -> know
  • at the beginning when enumerating: committing -> commit other verbs too (use infinitive not +ing

[ctmbl]

I just reviewed it @ZynoXelek great article indeed!!

Just 2 things beofre the merge:

• [x] could you write a brief conclusion?
• [x] could you either:
  • add a summary
  • remove the summary attribute from the header and an auto generated summary will be displayed (basically the first 60 characters of the article)
  • remove the summary attribute and put this line somewhere to explicitely "cut" the summary