-
Notifications
You must be signed in to change notification settings - Fork 70
How we Git
Jeff Fredrickson edited this page Oct 28, 2016
·
5 revisions
The primary branch for development is dev. The master branch contains the production code. All changes should initially be made in or merged into dev. After the appropriate QA/review, dev (or tags made from dev) can be merged into master. Federalist continuously deploys master to production.
Any changes made to or merged into dev can be viewed on the development site: https://federalist.18f.gov/preview/GSA/open-gsa-redesign/dev/
When contributing to open.gsa.gov, we typically work on branches off of the main repo, not forks. What does this mean?
- Create a new branch
- Make changes in your branch
- Commit the changes in your branch
- Push your branch with commits to the repository
- Optional: After you push your branch to GitHub, preview what your changes will look like on Federalist by going to https://federalist.18f.gov/preview/GSA/open-gsa-redesign/YOUR_BRANCH_NAME (replace YOUR_BRANCH_NAME with the actual name of your branch)
- Open a pull request to merge your branch into the open-gsa-redesign
devbranch. - After a successful merge, delete your branch if you want
- Fork the repository
- Make changes in your fork
- Commit the changes in your fork
- Open a pull request to merge your changes into the open-gsa-redesign
devbranch.
- Basic info and schedule
- #GSAhackathon: Our hashtag for the day
- Food: Here are some nearby places
- Code of Conduct: Please review the event code of conduct
- Questions?