Special Note For Everyone

'''
HERE’S WHAT YOU NEED TO KNOW TO PARTICIPATE AND COMPLETE HACKTOBERFEST:

- Have 4 pull/merge requests accepted between October 1 and October 31 to complete Hacktoberfest
- The first 40,000 participants (maintainers and contributors) who complete Hacktoberfest can elect to receive one of two prizes:
a tree planted in their name, or the Hacktoberfest 2022 t-shirt.
- Always make more then 4 pull request
lets you have made only 4 pull request to different projects
but one project is excluded from hackoctoberfest event then your pull request will not be count and 
then you have remains 3 valid pull request if these projects is not excluded.
if you fail to make 4 pull request then you cant get swags or t-shirts.
i will recommend you make pull request to your own repo which is very very saffest side for you..
keep in mind that repo has hacktoberfest topic..
'''

Hacktoberfest 2022 🎉

🗣 Hacktoberfest encourages participation in the open source community, which grows bigger every year. Complete the 2022 challenge and earn a limited edition T-shirt.

📢 Register here for Hacktoberfest and make four pull requests (PRs) between October 1st-31st to grab free T-shirt and more.

Upload your File/Analysis report in this repository to particular section if folder is not present then create folder. Some more repos for contribution

Rules

• Don't use filthy words and be welcome for beginners and other people in this community.

---

Github Contribution Rules

• Pull requests can be submitted to any opted-in repository on GitHub or GitLab.
• The pull request must contain commits you made yourself.
• If a maintainer reports your pull request as spam, it will not be counted toward your participation in Hacktoberfest.
• If a maintainer reports behavior that’s not in line with the project’s code of conduct, you will be ineligible to participate.
• To get a shirt, you must make four approved pull requests (PRs) on opted-in projects between October 1-31 in any time zone.
• This year, the first 40,000 participants can earn a T-shirt.

---

Steps for adding your name below

1. Respond to my issues or create your own issue with a problem statement I will assign you with the issue
2. Fork this repo
3. Add your Analysis File/Dashboard/Report (Your choice) to `.contribution` directory.
4. Edit `CONTRIBUTERS.MD` file
5. Add your Name also link your github profile
6. Make pull request

Contributions of any kind welcome!

NOTE: if you should be on the list of contributors but we forgot you, don't be shy and let us know!

Getting Started 🤩🤗:

• Fork this repo (button on top)
• Clone on your local machine

git clone https://github.com/Nitin-Diwakar/Data-Science-Data-Analystics-Contribution---Hacktoberfest-2022.git

• Navigate to project directory.

cd Data-Science-Data-Analystics-Contribution---Hacktoberfest-2022

• Create a new Branch

git checkout -b my-new-branch

• Add your contribution

git add .

• Commit your changes.

git commit -m "Relevant message"

• Then push

git push origin my-new-branch

• Create a new pull request from your forked repository

Avoid Conflicts {Syncing your fork}

An easy way to avoid conflicts is to add an 'upstream' for your git repo, as other PR's may be merged while you're working on your branch/fork.

git remote add upstream https://github.com/Nitin-Diwakar/Data-Science-Data-Analystics-Contribution---Hacktoberfest-2022

You can verify that the new remote has been added by typing

git remote -v

To pull any new changes from your parent repo simply run

git merge upstream/master

This will give you any eventual conflicts and allow you to easily solve them in your repo. It's a good idea to use it frequently in between your own commits to make sure that your repo is up to date with its parent.

For more information on syncing forks read this article from Github.

License

To the extent possible under law, Nitin Diwakar has waived all copyright and related or neighboring rights to this work.