This project was created for testing CircleCI. (CircleCI) Continuous Integration and Deployment. This can run shell commands through github. This project was also created for testing Netlify. Netlify builds, deploys and hosts your front-end. This is being done through github.
Because CircleCI can test the build, Netlify is altered in this project to be deployed using CircleCI instead of the normal Git intergration. This is why this project has a branch called 'dummy' as Netlify will look for changes on that branch (which will never be updated).
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.
Deploys the build folder to netlify using environment variables.
NETLIFY_AUTH_TOKEN and NETLIFY_SITE_ID must be set for this to work.
Whenever a git commit is pushed to the master branch CircleCI will run .circleci config.yml.
In .circleci yarn netlify:deploy runs at the end which takes the build folder and sends it to Netlify.
The git repo must be integrated with both CircleCI & Netlify.