├── CONTRIBUTING.md ├── LICENSE ├── CODE_OF_CONDUCT.md └── README.md /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | We love pull requests from everyone. By participating in this project, you 4 | agree to abide by the [Contributor Covenant](http://contributor-covenant.org). 5 | 6 | ## Steps 7 | 8 | 1. [Fork](https://help.github.com/articles/fork-a-repo/) this project 9 | 2. [Clone](https://help.github.com/articles/fork-a-repo/#step-2-create-a-local-clone-of-your-fork) your forked version `git clone git@github.com:/hacktoberfest-practice.git` 10 | 3. Make changes 11 | 4. [Commit](https://help.github.com/articles/adding-a-file-to-a-repository-using-the-command-line/) your changes (write a short descriptive message of what you have done) 12 | 5. [Push](https://help.github.com/articles/pushing-to-a-remote/) your changes to your forked version 13 | 6. Go to original project on GitHub & Create a [Pull Request](https://help.github.com/articles/about-pull-requests/) 14 | 15 | **DONE** 16 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2021 CodeVisors 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | ankushsinghgandhi@gmail.com. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Attribution 70 | 71 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 72 | version 2.0, available at 73 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 74 | 75 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 76 | enforcement ladder](https://github.com/mozilla/diversity). 77 | 78 | [homepage]: https://www.contributor-covenant.org 79 | 80 | For answers to common questions about this code of conduct, see the FAQ at 81 | https://www.contributor-covenant.org/faq. Translations are available at 82 | https://www.contributor-covenant.org/translations. 83 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Hacktoberfest-2021-practice 2 | 3 | This repo is not included in the Hacktoberfest event, as it is for practice only 4 | 5 | We have other repositories in the organisation you can contribute to. If you would like to join our GitHub organisation, raise an issue on this repo [CodeVisors-Support](https://github.com/CodeVisors/support) 6 | 7 | --- 8 | 9 | # Hacktoberfest 10 | 11 | [What is it ?](https://youtu.be/tjH6txTiC6E) Click to watch the video for more details📽 12 | 13 | [![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-v2.0%20adopted-ff69b4.svg)](CODE_OF_CONDUCT.md) 14 | 15 | # Hacktoberfest Practice Pull Requests 16 | 17 | Repo for you to raise a Pull Request for practice. 18 | 19 | **Just add your name to the alphabetical list and optionally, a link to your GitHub account** 20 | 21 | ## How to contribute 22 | 23 | 1. Fork the project 24 | 2. Make any changes in your forked repo 25 | 3. On this repo, click `Pull Requests` and raise a `Pull Request` selecting your fork on the right drop down 26 | 27 | Questions can be asked by raising an `Issue`. 28 | 29 | ## How to clone repo and make changes locally 30 | 31 | ``` 32 | click on the clone button (green in colour). This gives you a copy of the project. Its now yours to play around with 33 | ``` 34 | 35 | - Using git on your local machine. Do this to download the forked copy of this repo to your computer 36 | 37 | ``` 38 | git clone https://github.com/yourGithubUsername/hacktoberfest-practice.git 39 | ``` 40 | 41 | - switch to the cloned folder. This can be done with Gitbash or the integrated terminal in the VSCode editor 42 | 43 | ``` 44 | cd hacktoberfest-practice 45 | ``` 46 | 47 | - Make a new branch. Your name would make a good branch because it's unique 48 | 49 | ``` 50 | git checkout -b 51 | ``` 52 | 53 | - Open the file `README.md` 54 | 55 | - #### Add your name to the section that is headed with your first initial. Then, add your name in alphabetical order of the second letter in your name. If the second letters are the same, order it in alphabetical order of the third, and so on. Next to it, add the link to your github username page. 56 | 57 | - For example , 58 | `- [Full Name](https://github.com/your-username)` 59 | 60 | - Stage your changes 61 | 62 | ``` 63 | git add README.md 64 | ``` 65 | 66 | - Commit the changes 67 | 68 | ``` 69 | git commit -m "Add " 70 | ``` 71 | 72 | - Check the status of your repository 73 | 74 | ``` 75 | git status 76 | ``` 77 | 78 | - Pushing your repository to github 79 | 80 | ``` 81 | git push origin 82 | ``` 83 | 84 | or 85 | 86 | ``` 87 | git branch -M main 88 | git push -u origin main 89 | ``` 90 | 91 | - Navigate to your fork, on the top of the files section you'll notice a new section containing, a contribute button! 92 | - Click on the contribute button, it will open a drop down, click the pull request button on the drop down 93 | Note: A pull request allows your changes to be merged with the original project. 94 | 95 | - Wait for your changes to be merged 96 | 97 | Hurray! You successfully made a contribution! 98 | 99 | --- 100 | 101 | ## What if I have a Conflict? 102 | 103 | #### A GitHub conflict is when people make changes to the same area or line in a file. This must be fixed before it is merged in order to prevent collision in the main branch. 104 | 105 | - #### To read more about this, go to [Github Docs - About Merge Conflicts](https://docs.github.com/en/github/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts) 106 | - #### To find out about how to fix a Git Conflict, go to [Github Docs - Resolve Merge Conflict](https://docs.github.com/en/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github) 107 | 108 | --- 109 | 110 | ## Hacktoberfest community 111 | 112 | - ### **A** 113 | 114 | - [Ankush Singh Gandhi](https://github.com/ankushsinghgandhi) 115 | - [Aditya Raj](https://github.com/adityaraj079) 116 | - [Aman Shrivastava](https://github.com/aman34503) 117 | - [Aman Upadhyay](https://github.com/AmanxUpadhyay) 118 | 119 | - ### **B** 120 | 121 | - ### **C** 122 | - [Chetan Thakral](https://github.com/chetan-2002) 123 | - [Chirag Taneja](https://github.com/chiragtaneja04) 124 | - ### **D** 125 | - [Dipak Bari](https://github.com/dipakbari4) 126 | - ### **E** 127 | 128 | - ### **F** 129 | 130 | - ### **G** 131 | 132 | - ### **H** 133 | - [Harshit Aditya](https://github.com/HarshitAditya27) 134 | - ### **I** 135 | - [Isha Mehta](https://github.com/isha614) 136 | - ### **J** 137 | 138 | - ### **K** 139 | 140 | - ### **L** 141 | 142 | - ### **M** 143 | 144 | - ### **N** 145 | 146 | - ### **O** 147 | 148 | - ### **P** 149 | 150 | - [Pranay Gupta](https://github.com/thepranaygupta) 151 | 152 | - ### **Q** 153 | 154 | - ### **R** 155 | 156 | - ### **S** 157 | 158 | - [Saurav Mukherjee](https://github.com/SauravMukherjee44) 159 | - [Souvik Mandal](https://github.com/8-bit-souvik) 160 | - [Shivam Hande](https://github.com/0shivamh) 161 | 162 | - ### **T** 163 | 164 | - ### **J** 165 | 166 | - ### **U** 167 | 168 | - ### **V** 169 | - [Vivek Kumar Gupta](https://github.com/vivek9386) 170 | - [Vikash Gupta](https://github.com/heyimvikash) 171 | 172 | - ### **W** 173 | 174 | - ### **X** 175 | 176 | - ### **Y** 177 | 178 | - ### **Z** 179 | --------------------------------------------------------------------------------