On 08/28/2015 10:28 AM, Peter W A Wood wrote:
On 28 Aug 2015, at 15:15, Richmond <richmondmathew...@gmail.com> wrote:

Well: as an almost complete newcomer to Github, I would be grateful if you 
could outline a way to edit
the documents at 
https://github.com/runrev/livecode-ide/tree/develop/Documentation/guides 
<https://github.com/runrev/livecode-ide/tree/develop/Documentation/guides> and 
submit them after
the editing . . . does this involve setting up my own github branch????
Yes. You will need a Github account and then fork the Github repository. You 
can then edit the documents on-line. Once you have finished editing the 
documents, you will need to create a Pull Request. The LiveCode team will then 
decide whether to accept or decline your changes.

One thing that is needed for your changes to be accepted is to for you to enter into 
a contributor’s agreement http://livecode.com/account/developer/contribute 
<http://livecode.com/account/developer/contribute>

You can make better use of Git by downloading the repository onto your own machine. I 
was able to do that quite easily by following this 
https://help.github.com/categories/bootcamp/ 
<https://help.github.com/categories/bootcamp/>

I have no doubt that you will breeze though the process.

I very much doubt it: I downloaded GIT,

told GIT my name ('richmond'),

told GIT my email ('richmondmathew...@gmail.com'),

and then got stuck:

https://help.github.com/articles/set-up-git/#next-steps-authenticating-with-github-from-git

so; where is GIT"

Richmond.

Peter

_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to