├── .github └── workflows │ └── greetings.yml ├── Campus Ambassador └── Readme.md ├── LICENSE ├── Mentors └── Readme.md └── README.md /.github/workflows/greetings.yml: -------------------------------------------------------------------------------- 1 | name: Greetings 2 | 3 | on: [pull_request_target, issues] 4 | 5 | jobs: 6 | greeting: 7 | runs-on: ubuntu-latest 8 | permissions: 9 | issues: write 10 | pull-requests: write 11 | steps: 12 | - uses: actions/first-interaction@v1 13 | with: 14 | repo-token: ${{ secrets.GITHUB_TOKEN }} 15 | pr-message: "Don't forget to [Star](https://github.com/Girlscript-WOB/Open-source-Practice) repo & follow me on [GitHub](https://github.com/Durgesh4993) :)" 16 | -------------------------------------------------------------------------------- /Campus Ambassador/Readme.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | # 8 | 9 | 10 | | Image |Name | Country | Who am I | LinkedIn, GitHub and Twitter| 11 | |------|--------|-----------------------|--------------------------------|-------------------| 12 | |

| Sayantan Patra| India | Software and Open Source Developer | - [LinkedIn](https://www.linkedin.com/in/sayantanpatra2004) - [GitHub](https://github.com/sayantancodex) - [Twitter](https://x.com/SayantanPatra_?s=09) | 17 | |

| Varsha U N| India | Open Source Enthusiast | - [LinkedIn](https://www.linkedin.com/in/varsha-un?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=android_app), - [GitHub](https://github.com/VarshaUN) | 20 | |

|Cheryl Lobo| India | Open Source Enthusiast | - [LinkedIn](https://www.linkedin.com/in/cheryl-lobo-0b7646254/), - [GitHub](https://github.com/cherylobo) - [Twitter](https://x.com/CherylLobo76415) | 36 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2024 Winter of Blockchain 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 | -------------------------------------------------------------------------------- /Mentors/Readme.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | # 9 | 10 | 11 | | Image |Name | Country | Who am I | LinkedIn, GitHub and Twitter| 12 | |------|--------|-----------------------|--------------------------------|-------------------| 13 | |

| Akshit Batra | India | Senior Application Developer, Web Application Developer | - [LinkedIn](https://www.linkedin.com/in/akshit-batra/) - [GitHub](https://github.com/akbatra567) - [Twitter](https://x.com/akbatra567) | 21 | |

|Aditya D| India | DevOps Engineer and Open Source Developer | - [LinkedIn](https://www.linkedin.com/in/aditya-d-23453a179/), - [GitHub](https://github.com/adi271001) - [Twitter](https://x.com/ADITYAD29257528) - [Topmate](https://topmate.io/aditya_d/)| 27 | |

| Garima | India | Developer, Designer & Cybersecurity Scholar | - [LinkedIn](https://www.linkedin.com/in/garima-shrivastav/), - [GitHub](https://github.com/techy4shri) 32 | 33 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Open-source-Practice 2 | Winter of Blockchain, founded by GirlScript Foundation India in 2022, is a 2-month open source program designed to empower blockchain enthusiasts. 3 | 4 | ## Open-Source-Practice Pull Requests 5 | 6 | Repository for you to raise a Pull Request to **practice** open-source! 🎉 7 | 8 | ### Add your name to the alphabetical list under WoB Community and, optionally, a link to your GitHub account (in alphabetical order below your letter too) 9 | 10 | ### Option 1. Complete this process in GitHub (in your browser) 11 | 12 | ```mermaid 13 | flowchart LR 14 | Fork[Fork the project]-->branch[Create a New Branch] 15 | branch-->Edit[Edit file] 16 | Edit-->commit[Commit the changes] 17 | commit -->|Finally|creatpr((Create a Pull Request)) 18 | ``` 19 | 20 | **1. Fork the project:** 21 | 22 | - Click the gray Fork button at the top right of the previous page. This creates your copy of the project and saves it as a new repository in your GitHub account. 23 | 24 | **2. Create a New Branch:** 25 | 26 | - On your new repository's page, click the gray main button in the upper left to reveal a dropdown menu. 27 | - Enter the name of your new branch in the text box. (Branch names usually refer to what is being changed. Example: nameAdd). 28 | -Click on Create branch , which will automatically take you to your new branch. You can make edits on the main branch, but this may cause issues down the line. The best practice is to create a new branch for each separate issue you work on. That way your main branch remains in sync with WoB's main branch. 29 | 30 | **3. Edit:** 31 | 32 | - On the top right of the Readme file, click on the pencil icon to edit the file by **adding your name and your GitHub profile link to the section that matches your Initial in [this list](https://github.com/Girlscript-WOB/Open-source-Practice/blob/main/README.md#WoB24-Community). Make sure that your name is in alphabetical order.** 33 | - After editing the Readme file, add a commit message (Added my name or it can be anything related to your commit) and click on the green button saying "Commit Changes". Make sure you have selected the branch you have created. 34 | 35 | **4. Raise a Pull Request:** 36 | 37 | - Click `Pull Requests` option in your forked repository (which is the third option at the top of this page after the options `Code` and `Issues`). 38 | - Click the green New Pull Request button. This will prep the new pull request for you by auto-filling the base repository: base with 'Open-source-Practice: main' AND auto-filling your head repository: compare with your repository: main 39 | - Click on your head repository's `compare` dropdown, and switch branches from your 'main' branch to ``. 40 | - Finally, click the green `Create Pull Request` button. Great job! You did it! 41 | 42 | You can ask questions by raising an [issue](https://github.com/Girlscript-WOB/Open-source-Practice/issues). 43 | 44 | ### Option 2. Complete this process on your computer (locally) 45 | 46 | **1. Fork the project:** 47 | 48 | - Click the gray Fork button at the top right of the previous page. This creates your copy of the project and saves it as a new repository in your GitHub account. 49 | 50 | **2. Clone this project on your computer:** 51 | 52 | - Go to your profile. You will find forked repo named **_open-source-practice_**. go to the repo by clicking on it. 53 | - Click on the green Code button, then either the HTTPS or SSH option, and, click the icon to copy the URL. Now you have a copy of the project. Thus, you can play around with it locally on your computer. 54 | 55 | - Run the following commands into a terminal window (Command Prompt, Powershell, Terminal, Bash, ZSH). Do this to download the forked copy of this repository to your computer. 56 | 57 | ```bash 58 | git clone https://github.com/Girlscript-WOB/Open-source-Practice.git 59 | ``` 60 | 61 | - Switch to the cloned folder. You can paste this command into the same terminal window. 62 | 63 | ```bash 64 | cd Open-source-Practice 65 | ``` 66 | 67 | **3. Open in code Editor:** 68 | 69 | - Open the `README.md` file 70 | 71 | **4. Create a new branch:** 72 | - Your username would make a good branch name because it's unique. 73 | 74 | ```bash 75 | git checkout -b 76 | ``` 77 | 78 | **5. Edit the File:** 79 | 80 | - **Add your name to the section that matches your Initial in [this list](https://github.com/Girlscript-WOB/Open-source-Practice/blob/main/README.md#WoB24-Community), make sure that your name is in alphabetical order.Then save your changes.** 81 | 82 | - For example 83 | `- [Full Name](https://github.com/your-username)` 84 | 85 | **5. Stage your changes:** 86 | 87 | ```bash 88 | git add README.md 89 | ``` 90 | 91 | or you can stage all the changes using- 92 | 93 | ```bash 94 | git add . 95 | ``` 96 | 97 | **6. Commit the changes:** 98 | 99 | ```bash 100 | git commit -m "Add " 101 | ``` 102 | 103 | - Check the status of your repository. 104 | 105 | ```bash 106 | git status 107 | ``` 108 | 109 | - The response should be like this: 110 | 111 | ```bash 112 | On branch 113 | nothing to commit, working tree clean 114 | ``` 115 | 116 | **7. Pushing your repository to GitHub:** 117 | 118 | ```bash 119 | git push origin 120 | ``` 121 | 122 | or 123 | 124 | ```bash 125 | git branch -M main 126 | git push -u origin main 127 | ``` 128 | 129 | > **Warning**: If you get an error message like the one below, you probably forgot to fork the repository before cloning it. It is best to start over and fork the project repository first. 130 | 131 | ```bash 132 | ERROR: Permission to https://github.com/Girlscript-WOB/Open-source-Practice denied to . 133 | fatal: Could not read from remote repository. 134 | Please make sure you have the correct access rights and that the repository exists. 135 | ``` 136 | 137 | **8. Raise a Pull Request:** 138 | 139 | - On the GitHub website, navigate to your forked repo - on the top of the files section, you'll notice a new section containing a `Compare & Pull Request` button! ![createpr] 140 | 141 | - Click on that button, this will load a new page, comparing the local branch in your forked repository against the main branch in the GirlScript-WOB Open-Source-Practice repository. Do not make any changes in the selected values of the branches (do so only if needed), and click the green `Create Pull Request` button. 142 | Note: A pull request allows us to merge your changes with the original project repo. 143 | 144 | - Your pull request will be reviewed and then eventually merged. 145 | 146 | Hurray! You successfully made your first contribution! 🎉 147 | 148 | --- 149 | 150 | ## How can I fix a merge conflict? 151 | 152 | 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 to prevent collision in the main branch. 153 | 154 | - **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)** 155 | 156 | - **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)** 157 | 158 | ## Video demonstration for Mentors and CAs to open pull requests 159 | 160 | https://github.com/user-attachments/assets/891b8824-6c71-4371-9797-5c2c7f157e6c 161 | 162 | 163 | 164 | 165 | ## Our Pledge 166 | 167 | We take participation in our community as a harassment-free experience for everyone and we pledge to act in ways to contribute to an open, welcoming, diverse and inclusive community. 168 | 169 | --------------------------------------------------------------------------------