Skip to content

Latest commit

 

History

History
164 lines (125 loc) · 6.79 KB

CONTRIBUTING.md

File metadata and controls

164 lines (125 loc) · 6.79 KB
Raw

Contributing Guidelines 📄

This documentation contains a set of guidelines to help you during the contribution process. We are happy to welcome all the contributions from anyone willing to improve/add new scripts to this project. Thank you for helping out and remember, no contribution is too small.
Please note we have a code of conduct please follow it in all your interactions with the project.

How to Contribute ?

Getting Started

  1. Clone the repo
 git clone https://github.com/anuragverma108/SwapReads
  1. Install npm packages
npm install
  1. Run index.html with any browser (example: chrome etc).

Contribution

Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

  • If you have any suggestions for the project, such as reporting a bug, improving the UI, or enhancing the README.md file, feel free to open an issue to discuss it or directly create a pull request with the necessary changes.
  • Please make sure to check your spelling and grammar.
  • Create individual pull requests for each suggestion to keep changes focused and manageable.

Your involvement helps to improve the project and make it better for everyone. Thank you for your contributions!

Creating Pull Request

  1. Fork the Project:

    • Click on the "Fork" button at the top right corner of the repository's page on GitHub to create your own copy of the project.

  2. Clone Your Forked Repository:

    • Clone the forked repository to your local machine using the following command:
     git clone https://github.com/<your_user_name>/SwapReads
    • Navigate to project folder:
     cd SwapReads

  3. Add a reference(remote) to the original repository:

    git remote add upstream https://github.com/anuragverma108/SwapReads

  4. Check the remotes for this repository.

    git remote -v

  5. Always take a pull from the upstream repository to your master branch to keep it at par with the main project (updated repository).

    git pull upstream main

  6. Create a New Branch and Move to the Branch:

    • Create a new branch for your changes and move to that branch using the following commands:
    git checkout -b <branch-name>

  7. Add Your Changes:

    • After you have made your changes, check the status of the changed files using the following command:
    git status -s
    • Add all the files to the staging area using the following command:
    git add .

    or add specific files using:

    git add <file_name1> <file_name2>

  8. Commit Your Changes:

    • Commit your changes with a descriptive message using the following command:
    git commit -m "<EXPLAIN-YOUR_CHANGES>"

  9. Push Your Changes:

    • Push your changes to your forked repository on GitHub using the following command:
    git push origin <branch-name>

  10. Open a Pull Request:

    • Go to the GitHub page of your forked repository, and you should see an option to create a pull request. Click on it, provide a descriptive title and description for your pull request, and then submit it.

Alternatively contribute using GitHub Desktop

  1. Open GitHub Desktop: Launch GitHub Desktop and log in to your GitHub account if you haven't already.

  2. Clone the Repository:

    • If you haven't cloned the SwapReads repository yet, you can do so by clicking on the "File" menu and selecting "Clone Repository."
    • Choose the SwapReads repository from the list of repositories on GitHub and clone it to your local machine.

  3. Switch to the Correct Branch:

    • Ensure you are on the branch that you want to submit a pull request for.
    • If you need to switch branches, you can do so by clicking on the "Current Branch" dropdown menu and selecting the desired branch.

  4. Make Changes: Make your changes to the code or files in the repository using your preferred code editor.

  5. Commit Changes:

    • In GitHub Desktop, you'll see a list of the files you've changed. Check the box next to each file you want to include in the commit.
    • Enter a summary and description for your changes in the "Summary" and "Description" fields, respectively. Click the "Commit to " button to commit your changes to the local branch.

  6. Push Changes to GitHub: After committing your changes, click the "Push origin" button in the top right corner of GitHub Desktop to push your changes to your forked repository on GitHub.

  7. Create a Pull Request:

  • Go to the GitHub website and navigate to your fork of the SwapReads repository.
  • You should see a button to "Compare & pull request" between your fork and the original repository. Click on it.

  1. Review and Submit:

    • On the pull request page, review your changes and add any additional information, such as a title and description, that you want to include with your pull request.
    • Once you're satisfied, click the "Create pull request" button to submit your pull request.

  2. Wait for Review: Your pull request will now be available for review by the project maintainers. They may provide feedback or ask for changes before merging your pull request into the main branch of the SwapReads repository.

Issue Report Process 📌

  1. Go to the project's issues.
  2. Give proper description for the issues.
  3. Don't spam to get the assignment of the issue 😀.
  4. Wait for till someone is looking into it !.
  5. Start working on issue only after you got assigned that issue 🚀.

Pull Request Process 🚀

  1. Ensure that you have self reviewed your code 😀
  2. Make sure you have added the proper description for the functionality of the code
  3. I have commented my code, particularly in hard-to-understand areas.
  4. Add screenshot it help in review.
  5. Submit your PR by giving the necesarry information in PR template and hang tight we will review it really soon 🚀

Need some help regarding the basics?🤔

You can refer to the following articles on basics of Git and Github and also contact the Project Mentors, in case you are stuck:

Thank you for contributing💗