-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
657d658
commit 6474658
Showing
1 changed file
with
65 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
# e_learning_website | ||
|
||
|
||
|
||
1. give star on the repo | ||
2. create own issue | ||
3. fork the repo | ||
4. clone forked repo on your local system | ||
5. do change | ||
6. do valid commit | ||
7. push the changes | ||
8. create Pull Request | ||
9. wait for merge | ||
|
||
|
||
# Hacktoberfest Contribution Guide for Students | ||
|
||
Welcome to Hacktoberfest, a month-long celebration of open source! As a student, you can actively participate in this event by contributing to various projects on GitHub. This guide will walk you through the process of making a meaningful contribution and getting involved in the open source community. | ||
|
||
## How to Contribute: | ||
|
||
### 1. Give a Star to the Repository: | ||
Start by showing your support! Give a star to the repository you are interested in contributing to. This helps the project gain visibility among other developers. | ||
|
||
### 2. Create Your Own Issue: | ||
Before making changes, it's good practice to check if the project has existing issues or create one if you find something that needs improvement or fixing. Issues are a great way to communicate with the maintainers and other contributors about what you are working on. | ||
|
||
### 3. Fork the Repository: | ||
Click the "Fork" button in the upper right corner of the repository's page. This creates a copy of the repository under your GitHub account, allowing you to freely experiment with changes without affecting the original project. | ||
|
||
### 4. Clone the Forked Repository to Your Local System: | ||
Use `git clone` to copy the repository to your local machine. This will create a local copy that you can work on. | ||
|
||
```bash | ||
git clone https://github.com/your-username/repository-name.git | ||
cd repository-name | ||
``` | ||
|
||
### 5. Make Changes: | ||
Make the necessary changes to the project. Whether it's fixing a bug, adding a feature, or improving documentation, your contributions are valuable. | ||
|
||
### 6. Commit Your Changes: | ||
Once you've made your changes, stage and commit them with a clear and descriptive commit message. | ||
|
||
```bash | ||
git add . | ||
git commit -m "Brief description of your changes" | ||
``` | ||
|
||
### 7. Push the Changes: | ||
Push your commits to your forked repository on GitHub. | ||
|
||
```bash | ||
git push origin master | ||
``` | ||
|
||
### 8. Create a Pull Request (PR): | ||
Go to your forked repository on GitHub and click on the "New Pull Request" button. Provide a detailed description of your changes in the PR template. This helps the maintainers understand your contribution. | ||
|
||
### 9. Wait for Merge: | ||
After creating the pull request, the project maintainers will review your changes. Be patient and be open to feedback. You might need to make additional changes based on the feedback received. | ||
|
||
Congratulations on making your contribution to Hacktoberfest! Remember, open source is about collaboration and learning from each other. Happy coding! 🚀 | ||
|
||
**Note:** Please refer to the project's specific guidelines and code of conduct for any additional instructions or requirements regarding contributions. |