A 17 de janeiro de 2020 21:44:00 CET, ToddAndMargo via perl6-users <perl6-us...@perl.org> escreveu: >On 2020-01-17 12:20, Trey Harris wrote: >> If the issue is that you aren’t comfortable enough with Git¹, I assume >> as part of the basic toolkit of a sysadmin you know how to generate a >> unified diff patchfile (with `diff -ruN` or equivalent)? >> >> If so, if you generate one and upload it attached to a GitHub issue, we >> can figure out how to turn it into a PR rather trivially (and if I’m the >> first to pick it up, I’ll include step-by-step instructions on how to do >> it as a Git PR in the future). > >Now I am confused. Exactly what is going on with a PR? > >What I am after is to add an example to a document page. >Is there any special thing about this other than just >asked for it? It sounds like I download my own copy >of the page (with git), then make the alterations, >then request others evaluate it? > >Your in confusion, >-T
Offlist Git is a distributed version control system. This means that you create copies of the original (upstream) repo (hence the distributed part). This is a very simplified explanation: So you do your changes and commit on your repo. Since you want your changes to go to upstream, you need to create a pr (pull request). Github helps in this, which means that you push your changes to your repo in github (assuming that you forked to your account in github), also known as origin, and on github a link will appear to create a pull request. If you click on that link, you will be redirected to the create pull request page, where you can see your changes. Then the pr needs to be aproved to be merged into upstream, you might get some comments with changes you need to do and so. You then just commit the new changes and push them to your repo in git and the pr is updated. This is just one of many workflows possible with git. Let me know if you have questions Regards, David -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
