A simple to-do-list webpage

• Do your work
• After your work kindly add a screen shot of that
• Then do a Pull Request
• We will merge if we find it helpful

• Take a look at the Existing [Issues] or create your own!
• Fork the Repo and create a Branch for any Issue that you are working upon.
• Create a Pull Request which will be promptly reviewed and suggestions would be added to improve it.
• Add Screenshots to help us know what this is all about.

1. Fork the repository by clicking on the Fork symbol at the top right corner.

2. Clone the forked repository.

   git clone https://github.com/Soumyajit2825/MESSI_MANIA.git

3. Navigate to the project directory.

   cd MESSI_MANIA

4. Create a new branch:

   git checkout -b YourBranchName

5. Make changes in source code.

6. Stage your changes and commit

   git add .
   git commit -m "<your_commit_message>"

7. Push your local commits to the remote repo.

   git push origin YourBranchName

8. Create a PR

Note If anyone contributes to this repository, then the changes will not be reflected in your local repository. For that:

9. Setup a reference(remote) to the original repository to get all the changes from the remote.

   git remote add upstream https://github.com/Soumyajit2825/MESSI_MANIA.git

10. Check the remotes for this repository.

   git remote -v

11. Fetching from the remote repository will bring in its branches and their respective commits.

   git fetch upstream

12. Make sure that you're on your master branch.

   git checkout master

13. Now that we have fetched the upstream repository, we want to merge its changes into our local branch. This will bring that branch into sync with the upstream, without losing our local changes.

   git merge upstream/master

Here are a few things you can do that will increase the likelihood of your pull request being accepted:

• Follow the style guide. Any linting errors should be shown when running npm test.
• Write and update tests.
• Keep your changes as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
• Write a good commit message.

Work in Progress pull requests are also welcome to get feedback early on, or if there is something blocking you from working further.

• How to Contribute to Open Source
• Using Pull Requests
• GitHub Help

Please make sure to update tests as appropriate.

MIT