- Contributors should fork this repo
- Changes should be made in feature branches in their own repo
- A feature is submitted to this repo via creating a GitHub Pull Request (PR)
- The Pull Request can then be merged by the contributor or another developer with commit access
- PR merging should be done using
Squash and Rebase
- Fork on GitHub (for example, into account
my-gh
) - On local machine...
cd <proj-dir>
git clone [email protected]:my-gh/spatial-suite-demo-webapp.git
cd spatial-suite-demo-webapp
- Add CrunchyData repo as remote
upstream
usinggit remote add upstream [email protected]:CrunchyData/spatial-suite-demo-webapp.git
- Check remotes:
git remote -v
- Synch with upstream:
git pull upstream master
- Start on master branch:
git checkout master
(confirm withgit status
) - Synch with upstream:
git pull upstream master
- Create feature branch:
git checkout -b new-feature
- Make changes
- Review changes with
git status
- Stage changes:
git add -A
orgit add ...
- Commit changes:
git commit -m 'msg about new feature'
- Push to fork repo:
git push
- On GitHub fork, switch to branch and click [Create Pull Request]
- On GitHub CrunchySpatial, review PR
- Fix any conflicts (voodoo goes here - more info needed)
- Merge PR using [Squash and Rebase]
- Delete the fork feature branch
- Switch to master branch:
git checkout master
- Synch with upstream:
git pull upstream master
- IF all is well, delete feature branch:
git branch -D new-feature