Procedure questions on a GitHub Pull Request from a first time total noob

Wed 2018.11.07

'because all the work in progress forks end up public'

Most likely why I'm seeing 60+ changes/files appended with the desired branch during PR

Thank you @allObjects for the numbered instructions with annotations. That should help us all refer to a common sequence step.

I asked this several times, but still not sure if this will have caused issues, See #7 pull request above:

ref: http://www.espruino.com/Writing+Modules

I made it to the third from the end line:

'When you have it all as you want, . . . . click on Pull Request'

but the buttons were un-hilighted, so was unable to continue.

So, the Weekend Plan:

Start early, hot pot of coffee, phone off hook, loud Rock-n-Roll,
start with 1972 Steely Dan - Reelin' In the Years, (turn up volume before clicking play for best guitar riff intro effect)

https://www.youtube.com/watch?v=_bwHK1xk­gJA

Rev   'er up, dump the clutch,    begin . . . .


1) Delete old repo
If all goes well and above PR attempt doesn't block progress:
2) Create forked copy
3) Create clone of that
Using ao 10, 11, 12
4) Create branch and add files - commit
5) Create Pull Request from clone to fork
6) Create Pull Request from fork to espruino\EspruinoDocs

If that fails, or a hint of, 2nd pot of coffee, louder Rock-n-Roll

Read up on and install local copy and start with ao 1)

Have I got it?