Quiz Webapp client
Contributions are always welcome!
See Contributing for ways to get started.
Please adhere to this project's code of conduct.
Step 1: Fork the repository
Fork this repository by clicking on the fork button on the top of this page. This will create a copy of this repository in your account.
Now clone the forked repository to your machine. Go to your GitHub account, open the forked repository, click on the code button and then click the copy to clipboard icon.
Open a terminal and run the following git command:
git clone https://github.com/mlsacbvp/quiz-webapp-clientGo to the MLSAC project repository => In the Issues section => Choose an issue you think you can resolve => Comment that you want to work on it.
If the issue is assigned to you, you can work on it and send a PR within 2-3 days after syncing new changes.
- Without any assigned issue, don’t send a PR, and if you don’t find issues at a particular time, then visit the repo after 2-3 days.
- If you send a PR without being assigned an issue, your PR will be marked “spam” or “invalid”.
- After getting assigned an issue, you must send a PR within 2-3 days otherwise we will re-assigning that issue to someone else.
- https://hacktoberfest.com/participation/#pr-mr-details
- https://hacktoberfest.com/participation/#spam
- What is Hacktoberfest
- How to Use git
- how-to-contribute
- first-contributions
- awesome-for-beginners
- github-git-cheat-sheet
- How to Write Good Commit Messages
- How to Do Your First Pull Request? (video)
To deploy this project run
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may 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.