Home
This video shows generally how we will be using GitHub to stay organized and collaborate.
- Fork the upstream repo
- Clone your fork to your computer
- Merge from Upstream
- Click the branch menu
- Click the button "Choose a branch to merge into master"
- Select Upstream
- Click the button "Merge into master"
(Full article: https://github.com/team-refcode/refcode.org/wiki/How-to-contribute-to-Refcode1.0)
It's possible to have branches that don't track your fork, but track upstream instead. In fact, you will need to use branches that track upstream in order to contribute to the old codebase, which is on upstream refcode1.0. This video explains it:
Code merged into master is not automatically deployed to refcode.org. Instead, it is deployed to a staging area that is visible at https://master--refcode.netlify.com/.
In order for code to be visible on refcode.org, it must be merged into the prod branch. After any merge to prod everything on that branch will be deployed to refcode.org and will "go live" within minutes.
Netlify is the web server that hosts refcode.org and manages the deployment.
The pattern library can be viewed at https://master--refcode.netlify.com/patternlibrary.html.