A wesbite for Hack Upstate's Careers in Code
Careers in Code is Hack Upstate’s new initiative to help advance Central New York’s tech community by offering computer programming education to help fight poverty. It is a 24-week program aimed at women and minorities from distressed areas of central New York — poverty in these neighborhoods means residents don’t have equal opportunities to access education and employment opportunities, and our bootcamp was created to help close this gap and increase our region’s economic potential.
- Clone down the code:
git clone https://github.com/hackupstate/careers-in-code-website.git - When you are creating your remote origin, remember that you should NOT be using the master branch. Instead, contact Will or Jesse to has set up an individual branch. This repo utilizes pull requests for content management.
- Once cloned and initialized properly, try pushing a commit to your branch. In some cases, you may need to push to the HEAD, which would change your push message (ie. git push origin HEAD:dev).
For the purposes of version tracking and team management, we will be using Pull Requests to manage all pushes to master. This is a really great tool for team use on Git as it minimizes the possibility of messing up the main website and helps keep your version separate (allowing you to experiment with no worries, etc.). This also allows the team manager to review code independently before it goes live (Netlify’s prod feature is great for this!).
Once you have developed a particular feature and are ready for review, follow these steps:
- Commit and push your code to your own branch. Remember that since you are working on a team, people can’t read your mind. Be specific enough in your commit messages to let us know what you worked on.
- Once you have committed your code, go to the Github website, and navigate to your branch. Next to the branch selector above the code section, click “New Pull Request.” Github should automatically have your branch pulling into master.
- In this dialogue, you can edit your commit message and request reviewers on the right hand side, if necessary (you should be doing this most of the time for Will).
- Send the request and notify your reviewer on Slack (for some reason we don’t always get an email).
- If your code is good, (yay!), then the reviewer will merge it with master. If any changes are necessary, you do not need to submit another PR. Simply push the new version of your code to your own branch. Github will automatically add your changes to the existing PR and update the review guide for your reviewer. Here, it’s especially important to keep your commit messages specific as things get added under that assumption.