- Nik Osvalds
- Richard Stibbard
- Kieran Cott
- Henry MacFarlane
Never commit directly to the master branch. Create a new feature branch from the development branch, and make a pull request for a team-mate to review and merge.
- Clone the repository to your local machine using the URL in the Repo
git clone {url} {foldername}- Install neccessary packages using npm
npm install-
Find a new task in the task-list to work on (either Github issues or Trello)
-
Create a branch on your local machine to work on that issue/feature
git checkout -b {name of branch}-
Develop your features in your feature branch, and test on your local machine
-
Once you're happy with your branch push your branch to the remote repo on gitHub
git push origin {branch}-
In gitHub create a pull request for your new branch, assign a reviewer from the team (probably your other teammate) and link the issue you were working on (if it's a gitHub issue)
-
Have a team member review the pull request and merge!
-
Ensure the branch is deleted once its merged
- To test the front end fully you'll need to set up a local instance of the API on a VM. Follow the instructions on this gitHub repo to install:
(https://hopper.developme.space/api/
npm run deploy- The above command uses the gh-pages package to deploy to gitHub pages. Script lives in package.json and runs:
react-scripts build
gh-pages -d build
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify