Nice Job Pete. Before GitHub for Windows i was using SmartGit, which has more features and power but also can be quite confusing at times. So for my basic needs GitHub for Windows works fine. I would recommend adding a small section about contributing to existing projects. It's not that hard an can be useful, even if all you did was correct some typos or indenting in the PW codebase, like i've done in the past being the coding lightweight that i am. All little things count.
In a nutshell:Fork
- Go to https://github.com/r...ign/ProcessWire
- Click the "Fork" button in the top-right corner
- Visit your own PW fork page if your not already taken there automatically (https://github.com/MY_USERNAME
- Click "Clone in Windows" in the top-left corner.
- This will open up "GitHub for Windows" and after a short wait you will see a local repo of your fork.Configure remotesConfigure remotes
This allows you keep in sync with changes made to the original codebase (e.g. Ryan's repo)
- In "GitHub for Windows" local repositories view, right-click and choose "open a shell here"
- This will open a shell already in the right directory. Type the following commands:
git remote add upstream https://github.com/ryancramerdesign/ProcessWire.git # Assigns the original repo to a remote called "upstream"
git fetch upstream # Pulls in changes from the original repo not present in your local repository, without modifying your files. Allows you to review first.
git merge upstream/master # merge fetched changes into your working files.
Syncing and pull request
If you've merged upstream changes you can then sync them with your GitHub fork via the 'sync' button.
The same goes for changes you made yourself. If you think PW would benefit from these changes you can send a pull request. Go to your fork on GitHub and click the button "Pull Request".
- out of time -
Anyways, you've put it in pdf but is it an idea to put it on wiki.processwire.com as well?