├── CODEOWNERS
├── preptember-participants-2025.md
├── .github
    ├── ISSUE_TEMPLATE
    │   ├── add_participant.yml
    │   └── add_repository.yml
    └── pull_request_template.md
├── past-preptembers
    ├── preptember-participants-2024.md
    ├── repositories-list-2024.md
    ├── preptember-participants-2023.md
    └── repositories-list-2023.md
├── LICENSE
├── README.md
├── repositories-list-2025.md
└── CONTRIBUTING.md


/CODEOWNERS:
--------------------------------------------------------------------------------
1 | # Code Owners
2 | # see https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
3 | 
4 | * @Virtual-Coffee/maintainers
5 | * @Virtual-Coffee/hacktoberfest-team
6 | 


--------------------------------------------------------------------------------
/preptember-participants-2025.md:
--------------------------------------------------------------------------------
1 | # Preptember Participants
2 | 
3 | <!-- Add yourself to this file with your name, link to your GitHub profile, and your favorite book (and its author). -->
4 | 
5 | <!-- Please don't type or change anything above here. Work on your changes below. -->
6 | 
7 | - [Ayu Adiati](https://github.com/adiati98) | "The Subtle Art of Not Giving a Fuck" by Mark Manson
8 | - [Sara Baqla](https://github.com/missatrox44) | "The Measure" by Nikki Erlick


--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/add_participant.yml:
--------------------------------------------------------------------------------
 1 | name: ➕ Add participants
 2 | description: Add participants to vc-preptember
 3 | title: "Feature: Add <YOUR-NAME> as a Preptember Participant"
 4 | labels: [💡 feature]
 5 | body:
 6 |   - type: textarea
 7 |     attributes:
 8 |       label: Description
 9 |       description: Please describe the issue — for example, "For the VC Preptember challenge, I want to add myself as a participant."
10 |     validations:
11 |       required: true
12 |   - type: textarea
13 |     attributes:
14 |       label: Suggested solution
15 |       description: Suggest a solution — for example, "Add <YOUR-NAME> as a participant."
16 |   - type: checkboxes
17 |     id: terms
18 |     attributes:
19 |       label: Code of Conduct
20 |       description: By submitting this issue, you agree to follow our [Code of Conduct](https://virtualcoffee.io/code-of-conduct)
21 |       options:
22 |         - label: I agree to follow this project's Code of Conduct
23 |           required: true
24 | 


--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/add_repository.yml:
--------------------------------------------------------------------------------
 1 | name: 📃 Add repositories
 2 | description: Add repositories to vc-preptember
 3 | title: "Feature: Add <REPOSITORY-NAME> to the Repositories List"
 4 | labels: [💡 feature]
 5 | body:
 6 |   - type: textarea
 7 |     attributes:
 8 |       label: Description
 9 |       description: Please describe the issue — for example, "For the VC Preptember challenge, I want to add repositories I recommend for Hacktoberfest."
10 |     validations:
11 |       required: true
12 |   - type: textarea
13 |     attributes:
14 |       label: Suggested solution
15 |       description: Suggest a solution — for example, "Add <REPOSITORY-NAME> to the recommended repositories for Hacktoberfest."
16 |   - type: checkboxes
17 |     id: terms
18 |     attributes:
19 |       label: Code of Conduct
20 |       description: By submitting this issue, you agree to follow our [Code of Conduct](https://virtualcoffee.io/code-of-conduct)
21 |       options:
22 |         - label: I agree to follow this project's Code of Conduct
23 |           required: true
24 | 


--------------------------------------------------------------------------------
/past-preptembers/preptember-participants-2024.md:
--------------------------------------------------------------------------------
 1 | # Preptember Participants
 2 | 
 3 | <!-- Add yourself to this file with your name, link to your GitHub profile, and your favorite cake or snack. -->
 4 | 
 5 | <!-- Please don't type or change anything above here. Work on your changes below. -->
 6 | 
 7 | - [Ayu Adiati](https://github.com/adiati98) | Black Forest cake
 8 | - [Christine Belzie](https://github.com/CBID2) | Red Velvet cake
 9 | - [Meg Gutshall](https://github.com/meg-gutshall) | ICE CREAM!!!! 🍨🍨
10 | - [Micha Rodriguez](https://github.com/michaella23) | Cherries 🍒😊
11 | - [Pat Smith](https://github.com/patasmith) | Yellow cake with chocolate icing
12 | - [BekahHW](https://github.com/BekahHW) | Tiramisu
13 | - [Danielle Andrews](https://github.com/DrAcula27) | Cookie Cake 🍪
14 | - [Alicia Bendz](https://github.com/albendz) | Tres Leches
15 | - [Silvia Reyes](https://github.com/NathaliaReyes) | Genoese 🎂
16 | - [David Akim](https://github.com/david-001) | Internet 🔗🌐
17 | - [Dominic Duffin](https://github.com/dominicduffin1) | White Chocolate & Raspberry
18 | - [Christina Loiacono](https://github.com/christina-ml) | Cheesecake 🍰
19 | 


--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
 1 | MIT License
 2 | 
 3 | Copyright (c) 2023 Virtual Coffee
 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 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
 1 | # Welcome Preptember!
 2 | 
 3 | This is a special repository for **Virtual Coffee members** to prepare themselves for Hacktoberfest by practicing open source and listing VC-verified repositories we can recommend for Hacktoberfest.
 4 | 
 5 | ---
 6 | 
 7 | 📢 **Only PRs from existing Virtual Coffee members will be accepted.**
 8 | 
 9 | ---
10 | 
11 | You can watch our video walkthrough to learn more about this repository and how to contribute:
12 | 
13 | https://github.com/dominicduffin1/vc-preptember/assets/26224873/4fa3e1b3-bd8a-4ce8-9329-044c30e80fe8
14 | 
15 | ## 🤝 Contributing
16 | 
17 | See our [contributing guide](CONTRIBUTING.md) for detailed information and instructions on contributing to this repository.
18 | 
19 | ## 💭 Do you have questions?
20 | 
21 | Whenever you need help, you can ask for it in the `#open-source` or `#help-and-pairing` channels in Slack. You can also read our [guide on how to ask questions](https://virtualcoffee.io/resources/developer-resources/developer-tips/asking-coding-questions).
22 | 
23 | We're here to help you! 💙
24 | 
25 | ## ☕ Join Virtual Coffee Community
26 | 
27 | If you're interested in joining our community, you can learn about us through [our website](https://virtualcoffee.io/) and [join the waitlist](https://virtualcoffee.io/join).
28 | 
29 | ## ⚖️ License
30 | 
31 | [MIT © 2023 Virtual Coffee](LICENSE)
32 | 


--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
 1 | ## Slack Display Name
 2 | 
 3 |  <!-- Please provide your Slack Display Name at Virtual Coffee for us to confirm. -->
 4 | 
 5 | > [!Warning]
 6 | > Only PRs from existing Virtual Coffee members will be accepted.
 7 | 
 8 | ## Linked Issue
 9 | 
10 | <!--
11 | 
12 | Please link to your issue number that you can find after your issue's title.
13 | 
14 | To link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request, type the keyword "Closes" followed by a reference to the issue. For example, Closes #404.
15 | 
16 |  -->
17 | 
18 | ## Type of Contribution
19 | 
20 | <!--
21 | 
22 | Check the item(s) that applies. For example:
23 | 
24 | - [x] 🌱 Practice Open Source
25 | - [ ] 📃 Repositories List
26 | 
27 | -->
28 | 
29 | - [ ] 🌱 Practice Open Source
30 | - [ ] 📃 Repositories List
31 | 
32 | <br>
33 | 
34 | > [!NOTE]
35 | > If your type of contribution is 📃 **Repositories List**, check items in the repository checklist below that apply. We only accept PRs where most of the items are checked.
36 | 
37 | - [ ] Relevant name
38 | - [ ] Description
39 | - [ ] Relevant tags
40 | - [ ] README file
41 | - [ ] CONTRIBUTING file
42 | - [ ] Open source license
43 | - [ ] Code of Conduct (COC)
44 | - [ ] Issue and Pull Request templates
45 | 
46 | ## Description
47 | 
48 | <!-- Describe the changes that you've made in this PR. For example, "This PR adds <your-name> to the Preptember participants" or "This PR adds <repository-name> to the Repositories List." -->
49 | 


--------------------------------------------------------------------------------
/repositories-list-2025.md:
--------------------------------------------------------------------------------
 1 | # Repositories List
 2 | 
 3 | <!-- Before adding a repository to this list, make sure that it passes our repository checklist below -->
 4 | 
 5 | <!--
 6 | ✅ Relevant name
 7 | ✅ Description
 8 | Clearly describe what the project does and is for.
 9 | ✅ Relevant tags
10 | They should highlight their scope, stack, field, etc.
11 | ✅ README file
12 | Important information about your project.
13 | ✅ CONTRIBUTING file
14 | A contribution guide for contributors.
15 | ✅ Open source license
16 | A project is not open source if it doesn't have a valid license.
17 | ✅ Code of Conduct (COC)
18 | An excellent indicator of a healthy contributor's environment.
19 | ✅ Issue and Pull Request templates
20 | Templates for making issues and pull requests.
21 |  -->
22 | 
23 |  <!-- Please don't type or change anything above here. Work on your changes below. -->
24 | 
25 | - [virtualcoffee.io](https://github.com/Virtual-Coffee/virtualcoffee.io)
26 | - [Hacktoberfest HOWTO blog](https://github.com/hacktoberfesthowto/howto-blog)
27 | - [RepoReady](https://github.com/OpenSource-Communities/RepoReady)
28 | - [VC Community Docs](https://github.com/Virtual-Coffee/VC-Community-Docs)
29 | - [Intro to Open Source and Becoming a Maintainer Courses](https://github.com/OpenSource-Communities/intro)
30 | - [Continue](https://github.com/continuedev/continue/)
31 | - [Mautic User Docs](https://github.com/mautic/user-documentation)
32 | - [Mautic Low/No Code](https://github.com/mautic/low-no-code)
33 | - [Mautic Community Handbook](https://github.com/mautic/mautic-community-handbook)
34 | 


--------------------------------------------------------------------------------
/past-preptembers/repositories-list-2024.md:
--------------------------------------------------------------------------------
 1 | # Repositories List
 2 | 
 3 | <!-- Before adding a repository to this list, make sure that it passes our repository checklist below -->
 4 | 
 5 | <!--
 6 | ✅ Relevant name
 7 | ✅ Description
 8 | Clearly describe what the project does and is for.
 9 | ✅ Relevant tags
10 | They should highlight their scope, stack, field, etc.
11 | ✅ README file
12 | Important information about your project.
13 | ✅ CONTRIBUTING file
14 | A contribution guide for contributors.
15 | ✅ Open source license
16 | A project is not open source if it doesn't have a valid license.
17 | ✅ Code of Conduct (COC)
18 | An excellent indicator of a healthy contributor's environment.
19 | ✅ Issue and Pull Request templates
20 | Templates for making issues and pull requests.
21 |  -->
22 | 
23 |  <!-- Please don't type or change anything above here. Work on your changes below. -->
24 | 
25 | - [virtualcoffee.io](https://github.com/Virtual-Coffee/virtualcoffee.io)
26 | - [Virtual Coffee Podcast Transcripts](https://github.com/Virtual-Coffee/podcast-transcripts)
27 | - [Codecademy Docs](https://github.com/Codecademy/docs)
28 | - [LinksHub](https://github.com/rupali-codes/LinksHub)
29 | - [OpenSauced Learning Path](https://github.com/open-sauced/intro)
30 | - [OpenSauced Pizza Verse](https://github.com/open-sauced/pizza-verse)
31 | - [freeCodeCamp](https://github.com/freeCodeCamp/freeCodeCamp/issues/56170) - [Hacktoberfest tracking issue](https://github.com/freeCodeCamp/freeCodeCamp/issues/56170)
32 | - [Evidently LLM Monitoring](https://github.com/evidentlyai/evidently)
33 | - [Ethereum website](https://github.com/ethereum/ethereum-org-website)
34 | - [Python Turtle Art Canvas](https://github.com/dominicduffin1/python-turtle-art-canvas)
35 | 


--------------------------------------------------------------------------------
/past-preptembers/preptember-participants-2023.md:
--------------------------------------------------------------------------------
 1 | <!-- Add yourself to this file with your name, link to your GitHub profile, and your favorite coffee (or any other drink that you like!) -->
 2 | 
 3 | <!-- Please don't type or change anything above here. Work on your changes below. -->
 4 | 
 5 | # Preptember Participants
 6 | 
 7 | - [Ayu Adiati](https://github.com/adiati98) | Latte macchiato
 8 | - [Dominic Duffin](https://github.com/dominicduffin1) | Hot chocolate _without_ cream and marshmallows
 9 | - [Michael Jolley](http://github.com/michaeljolley) | [Sloth Dispelling Breakfast Blend](https://madpriestcoffee.com/collections/coffee/products/sloth-dispelling-breakfast-blend) from Mad Priest Coffee (Black)
10 | - [BekahHW](https://github.com/bekahhw) | Coffee with a splash of half and half
11 | - [Christine Belzie](https://github.com/CBID2) | A nice cold Sprite and a cup of hot tea with no sugar
12 | - [David Akim](https://github.com/david-001) | Any cold drink e.g. Iced coffee or iced tea
13 | - [Teri Eyenike](https://github.com/terieyenike) | Cafe au Lait
14 | - [Adam Abundis](https://github.com/abuna1985) | Medium or dark roast coffee with whipped Italian crème creamer and cinnamon
15 | - [Ross Larson](https://github.com/zo0o0ot) | Flavored sparkling water, like Limoncello La Croix
16 | - [Angie Rodriguez](https://github.com/ARodriguezHacks) | Simple black medium roast, no cream or sugar
17 | - [Anshuman Sathua](https://github.com/anshu-21) | Red honey tea
18 | - [Cris Crawford](https://github.com/cmcrawford2) | Black coffee, slightly weak
19 | - [Tammy Miller](https://github.com/tgmiller5) | Green Tea
20 | - [Christina Loiacono](https://github.com/christina-ml) | Pumpkin Spice Latte
21 | - [Satoshi Shirosaka](https://github.com/Satoshi-Sh) | Kombucha
22 | - [David Salgado](https://github.com/davidgsalgado) | Black Coffe (Plain)
23 | - [Kirk Shillingford](https://github.com/tkshill) | Ice Cold Black Coffee
24 | - [Brenna Hettler](https://github.com/brennakh) | Matcha with oat milk
25 | 


--------------------------------------------------------------------------------
/past-preptembers/repositories-list-2023.md:
--------------------------------------------------------------------------------
 1 | # Repositories List
 2 | 
 3 | <!-- Before adding a repository to this list, make sure that it passes our repository checklist below -->
 4 | 
 5 | <!--
 6 | ✅ Relevant name
 7 | ✅ Description
 8 | Clearly describe what the project does and is for.
 9 | ✅ Relevant tags
10 | They should highlight their scope, stack, field, etc.
11 | ✅ README.md file
12 | Important information about your project.
13 | ✅ CONTRIBUTIONS.md/CONTRIBUTING.md file
14 | A contribution guide for contributors.
15 | ✅ Open source license
16 | A project is not open source if it doesn't have a valid license.
17 | ✅ Code of Conduct (COC)
18 | An excellent indicator of a healthy contributor's environment.
19 | ✅ Issue and Pull Request templates
20 | Templates for making issues and pull requests.
21 |  -->
22 | 
23 |  <!-- Please don't type or change anything above here. Work on your changes below. -->
24 | 
25 | - [Virtual Coffee / virtualcoffee.io](https://github.com/Virtual-Coffee/virtualcoffee.io)
26 | - [Virtual Coffee / podcast transcripts](https://github.com/Virtual-Coffee/podcast-transcripts)
27 | - [freeCodeCamp's Developer Quiz Site](https://github.com/freeCodeCamp/Developer_Quiz_Site)
28 | - [EddieHubCommunity / BioDrop](https://github.com/EddieHubCommunity/BioDrop)
29 | - [LinksHub](https://github.com/rupali-codes/LinksHub)
30 | - [Codecademy/docs](https://github.com/Codecademy/docs)
31 | - [TheOdinProject/curriculum](https://github.com/TheOdinProject/curriculum)
32 | - [MDN Web Docs/content](https://github.com/mdn/content)
33 | - [OpenSauced/docs](https://github.com/open-sauced/docs)
34 | - [AccessibleForAll/AccessibleWebDev](https://github.com/AccessibleForAll/AccessibleWebDev)
35 | - [Intro to Open Source Course](https://github.com/open-sauced/intro/)
36 | - [OpenSauced Guestbook](https://github.com/open-sauced/guestbook)
37 | - [OpenSauced Pizza-Verse](https://github.com/open-sauced/pizza-verse)
38 | - [Python Turtle Art Canvas](https://github.com/dominicduffin1/python-turtle-art-canvas)
39 | - [Hacktoberfest HOWTO / Hugo static site](https://github.com/hacktoberfesthowto/howto-blog)
40 | - [Forem](https://github.com/forem/forem)
41 | - [Django link-in-bio tool](https://github.com/Terieyenike/linktree)
42 | - [Classic Memory Game](https://github.com/cmcrawford2/memory-game)
43 | - [Tiny Troves of Dev Wisdom](https://github.com/TarynMcMillan/Tiny-Troves-of-Dev-Wisdom)
44 | - [Elm RPG Session](https://github.com/tkshill/rpg-session/)
45 | - [SheSharp / Knowledge Hub](https://github.com/shesharpnl/knowledge-hub)
46 | 


--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
  1 | # Contributing Guide
  2 | 
  3 | ---
  4 | 
  5 | 📢 **Only PRs from existing Virtual Coffee members will be accepted.**
  6 | 
  7 | ---
  8 | 
  9 | Welcome to the contributing guide for Virtual Coffee's Preptember repo! Thank you so much for considering contributing to this repository 💙.
 10 | 
 11 | We take our [Code of Conduct](https://virtualcoffee.io/code-of-conduct/) very seriously, and all contributors must abide by it. Let’s treat each other with respect, and remember, we are all people who care and are trying. If you believe someone has violated the Code of Conduct, please fill out our [CoC Violation Form](https://virtualcoffee.io/report-coc-violation/), which you can do anonymously.
 12 | 
 13 | ## New Contributors
 14 | 
 15 | If you're new to open source, check out the resources below to help you familiarize yourself with Git, GitHub, and the contribution flow:
 16 | 
 17 | - [Virtual Coffee's Guide to Open Source](https://virtualcoffee.io/resources/developer-resources/open-source)
 18 | - [Intro to Open Source with OpenSauced](https://opensauced.pizza/learn/intro-to-oss)
 19 | - [Git and GitHub learning resources](https://docs.github.com/en/get-started/quickstart/git-and-github-learning-resources)
 20 | - [Git Guides](https://github.com/git-guides)
 21 | 
 22 | ## Contribution Type
 23 | 
 24 | You can make two types of contributions to this repo:
 25 | 
 26 | ### 1. 🌱 **Practicing Open Source**
 27 | 
 28 | Add your name, link to your GitHub profile, and your {favorite thing} to the `preptember-participants.md` file. Please read the comment in the file to find out what is the {favorite thing} of the year.
 29 | 
 30 | ### 2. 📃 **Repositories List**
 31 | 
 32 | Add the name and link to a repository you recommend for Hacktoberfest to the `repositories-list.md` file. Do this **_only after_** the repository meets our requirements — see our [repository checklist](https://virtualcoffee.io/resources/developer-resources/open-source/maintainer-guide#repository-checklist).
 33 | 
 34 | You can add multiple repositories here and you can always make another pull request if you have more for us later in the month!
 35 | 
 36 | ## Getting Started
 37 | 
 38 | We recommend you work on the changes in your local environment because most of the contribution process requires you to do so rather than directly on GitHub.
 39 | 
 40 | ### 1. Create an issue
 41 | 
 42 | 1. Click the `Issues` tab at the top.
 43 | 2. Click the green `New issue` button.
 44 | 3. Click the `Get started` button next to the `➕ Add participants` to add yourself as a Preptember participant or `📃 Add repositories` to add repositories to the list.
 45 | 4. Edit the title and complete the issue form.
 46 | 5. Click the green `Submit new issue` button at the bottom.
 47 | 
 48 | #### Additional Resources
 49 | 
 50 | - [Streamline Your Contributions: Mastering Issue Forms and PR Templates](https://dev.to/opensauced/streamline-your-contributions-mastering-issue-forms-and-pr-templates-36j5)
 51 | 
 52 | ### 2. Fork this repository
 53 | 
 54 | Click the `fork` button at the top of the front page.
 55 | 
 56 | Forking is a process to create a copy of this repository in your GitHub account. You always want to remember to fork a repository before cloning it.
 57 | 
 58 | ### 3. Clone the repository
 59 | 
 60 | Clone a repository means copying the remote repository into your local machine.
 61 | 
 62 | #### On GitHub
 63 | 
 64 | 1. Click your profile picture on the right top.
 65 | 2. Click "Your repositories".
 66 | 3. Open the forked repo by clicking on it.
 67 | 4. Click the green `<> Code` button.
 68 | 5. Click the copy icon to copy the HTTPS URL.
 69 | 
 70 | #### On your local machine
 71 | 
 72 | 1. In your terminal, run this command to create a copy of the forked repository in your local machine:
 73 | 
 74 |    ```bash
 75 |    git clone https_url
 76 |    ```
 77 | 
 78 |    Change the `https_url` with the HTTPS link that you've copied.
 79 | 
 80 | 2. Navigate to the directory where your local repository lives.
 81 | 
 82 |    ```bash
 83 |    cd vc-preptember
 84 |    ```
 85 | 
 86 | Remember that you always want to work on and push your changes into the forked repository, not the original one.
 87 | 
 88 | ### 4. Create a branch
 89 | 
 90 | A branch is an isolated environment to work on and save your changes. Later on, you will push this branch to the remote repository after you finish working on your changes.
 91 | 
 92 | Run the following command to create a branch:
 93 | 
 94 | ```bash
 95 | git checkout -b YOUR-BRANCH-NAME
 96 | ```
 97 | 
 98 | You can name the branch anything you want — for example, `alice-add-profile`.
 99 | 
100 | ### 5. Work on changes
101 | 
102 | #### 🌱 Practicing Open Source
103 | 
104 | 1. Open the `preptember-participants.md` file in VSCode or another text editor you use.
105 | 2. Add yourself to the file in this format:
106 | 
107 |    ```markdown
108 |    - [Your name](link to your GitHub profile) | your favorite thing
109 |    ```
110 | 
111 |    For example:
112 | 
113 |    ```markdown
114 |    - [User Name](https://github.com/username) | Favorite thing
115 |    ```
116 | 
117 | #### 📃 Repositories List
118 | 
119 | 1. Open the `repositories-list.md` file in VSCode or another text editor you use.
120 | 2. Add the repository(ies) that you recommend for Hacktoberfest. **Please make sure the repositories pass the [repository checklist](https://virtualcoffee.io/resources/developer-resources/open-source/maintainer-guide#repository-checklist) before you add them**.
121 | 
122 |    ```markdown
123 |    - [Organization / Repository Name](link to the repository)
124 |    ```
125 | 
126 |    For example:
127 | 
128 |    ```markdown
129 |    - [Virtual Coffee / virtualcoffee.io](https://github.com/Virtual-Coffee/virtualcoffee.io)
130 |    ```
131 | 
132 | ### 6. Add your changes
133 | 
134 | After you finish working on your changes, you must add them first. Adding changes means moving them into the staging area, where they will be ready to be saved (committed).
135 | 
136 | Run this command in your terminal:
137 | 
138 | ```bash
139 | git add .
140 | ```
141 | 
142 | This command will add all files with changes to the staging area.
143 | 
144 | ### 7. Commit your changes
145 | 
146 | Now, it's time to commit the changes. Committing changes means saving your changes.
147 | 
148 | Run the following command:
149 | 
150 | ```bash
151 | git commit -m "Your message"
152 | ```
153 | 
154 | Change `Your message` into your own message. For example:
155 | 
156 | ```bash
157 | git commit -m "Add Alice to Preptember participants"
158 | ```
159 | 
160 | 💡 **Good to know**:
161 | 
162 | When you make changes in an existing file, you can add and commit them all together with this command:
163 | 
164 | ```bash
165 | git commit -am "Your message"
166 | ```
167 | 
168 | ### 8. Push your changes
169 | 
170 | You want to push your changes to your remote (forked) repository. Run this command in your terminal:
171 | 
172 | ```bash
173 | git push -u origin YOUR-BRANCH-NAME
174 | ```
175 | 
176 | Change `YOUR-BRANCH-NAME` with the name of your working branch. For example:
177 | 
178 | ```bash
179 | git push -u origin alice-add-profile
180 | ```
181 | 
182 | ### 9. Create a pull request (PR)
183 | 
184 | 1. Go to your forked repository on GitHub.
185 | 
186 |    To ensure you're on the forked repo, look at the repo name on the top left beside the GitHub logo. It should have your GitHub username in the beginning: `your-username / repository-name`.
187 | 
188 | 2. Click the `Compare & pull request` green button on the top.
189 | 3. Fill in the pull request form.
190 | 4. Click the green `Create pull request` button on the bottom.
191 | 
192 | And that's it! Congratulations on your first contribution to this repo! 🎉
193 | 
194 | ## Resolve Merge Conflicts
195 | 
196 | You might encounter merge conflicts. When you encounter merge conflicts, you need to resolve them before your pull request can be merged into the `main` branch to avoid collision.
197 | 
198 | Merge conflicts usually occur when changes are on the same line(s), in the same file(s), from 2 different branches. It is common to encounter merge conflicts when contributing to open source.
199 | 
200 | ### Resources
201 | 
202 | - Virtual Coffee's Git & GitHub 101 guide to [resolving merge conflicts](https://virtualcoffee.io/resources/developer-resources/open-source/git-101#resolve-merge-conflicts).
203 | - [Resolving a merge conflict on GitHub](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github).
204 | - [How to Keep Branches Up-to-Date and Resolve Merge Conflicts in GitHub and VS Code](https://www.freecodecamp.org/news/keep-branches-up-to-date-resolve-merge-conflicts/)
205 | 
206 | ### Walkthrough Video
207 | 
208 | https://github.com/Virtual-Coffee/vc-preptember/assets/45172775/55a4e380-7b8b-4a36-a843-95237e66d4db
209 | 
210 | > [!TIP]
211 | >
212 | > - You can always ask for help in the `#open-source` or `#help-and-pairing` channel in Slack. We're here to help you! 💙
213 | > - We recommend resolving the merge conflicts in your local environment rather than directly on GitHub.
214 | > - For this contribution, we recommend you _accept both changes_.
215 | 
216 | ## Awaiting Review
217 | 
218 | Once you've submitted your pull request, the only thing left is to wait for feedback from one of the project maintainers. Since this is volunteer work for all, if it's been over **one week** and you have not received any acknowledgment, you can post a comment on your pull request reminding you of its status.
219 | 
220 | ## Suggested Changes
221 | 
222 | We may ask for changes before a pull request can be merged using [suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) or pull request comments.
223 | 
224 | As you update your pull request and apply changes, mark each conversation as [resolved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations).
225 | 


--------------------------------------------------------------------------------