|
| 1 | +# Contributing to Awesome GitHub Profiles |
| 2 | + |
| 3 | +Thank you for your interest in contributing to the **Awesome GitHub Profiles** project! We appreciate your time and effort. Follow the steps below to contribute successfully. |
| 4 | + |
| 5 | +## Getting Started |
| 6 | + |
| 7 | +### 1. Fork the Repository |
| 8 | + |
| 9 | +Click the **Fork** button at the top right of the repository page. This creates a copy of the repository under your GitHub account. |
| 10 | + |
| 11 | +### 2. Clone Your Fork |
| 12 | + |
| 13 | +After forking, clone your repository to your local machine: |
| 14 | + |
| 15 | +```bash |
| 16 | +git clone https://github.com/YOUR_USERNAME/awesome-github-profiles.git |
| 17 | +``` |
| 18 | + |
| 19 | +Replace `YOUR_USERNAME` with your GitHub username. |
| 20 | + |
| 21 | +### 3. Switch to the `gh-pages` Branch |
| 22 | + |
| 23 | +Since the main code is in the `gh-pages` branch, navigate to that branch after cloning: |
| 24 | + |
| 25 | +```bash |
| 26 | +cd awesome-github-profiles |
| 27 | +git checkout gh-pages |
| 28 | +``` |
| 29 | + |
| 30 | +### 4. Create a New Branch |
| 31 | + |
| 32 | +Create a new branch for your feature or bug fix: |
| 33 | + |
| 34 | +```bash |
| 35 | +git checkout -b your-feature-branch |
| 36 | +``` |
| 37 | + |
| 38 | +Use a descriptive name for your branch (e.g., `add-new-profile`, `fix-readme-typo`). |
| 39 | + |
| 40 | +### 5. Make Your Changes |
| 41 | + |
| 42 | +Make the necessary changes in your local repository. Follow the project's coding style and guidelines to ensure consistency. |
| 43 | + |
| 44 | +### 6. Test Your Changes |
| 45 | + |
| 46 | +If applicable, test your changes locally to ensure nothing breaks. This can include: |
| 47 | + |
| 48 | +- Running the project to verify functionality. |
| 49 | +- Running tests if the project includes any testing tools. |
| 50 | + |
| 51 | +### 7. Stage and Commit Your Changes |
| 52 | + |
| 53 | +Once your changes are made, stage the files you want to commit: |
| 54 | + |
| 55 | +```bash |
| 56 | +git add . |
| 57 | +``` |
| 58 | + |
| 59 | +Commit your changes with a clear message: |
| 60 | + |
| 61 | +```bash |
| 62 | +git commit -m "Add new profile" # Be specific about what changes were made. |
| 63 | +``` |
| 64 | + |
| 65 | +### 8. Push to Your Fork |
| 66 | + |
| 67 | +Push your new branch to your forked repository: |
| 68 | + |
| 69 | +```bash |
| 70 | +git push origin your-feature-branch |
| 71 | +``` |
| 72 | + |
| 73 | +### 9. Submit a Pull Request (PR) |
| 74 | + |
| 75 | +Navigate to the original repository on GitHub, and you should see an option to create a Pull Request. Click that and fill in the necessary details: |
| 76 | + |
| 77 | +- Reference any issue your PR addresses (e.g., "Closes #123"). |
| 78 | +- Explain clearly what your changes do. |
| 79 | + |
| 80 | +After submitting your PR, the maintainers will review it. You may receive feedback or requests for changes, so keep an eye on the comments. |
| 81 | + |
| 82 | +--- |
0 commit comments