Skip to content

Latest commit

 

History

History
99 lines (73 loc) · 5.1 KB

CONTRIBUTING.md

File metadata and controls

99 lines (73 loc) · 5.1 KB
Raw

Contributing Guidelines

This documentation contains a set of guidelines to help you during the contribution process.

I'm happy to welcome all the contributions from anyone willing to add new scripts to this repository. Thank you for helping out and remember, no contribution is too small.

Before Contributing

Welcome to shelcia/dynamic-portfolio. Before sending your pull requests, make sure that you read the whole guidelines. If you have any doubt on the contributing guide, please feel free to reach out.

Contribution

Any contribution is accepted, from fixing grammatical mistakes to implementing complex scripts. Please read this section if you are contributing your work.

Steps to Contribute

Following are the steps to guide you:

    • Step 1: Fork the repo and then follow the steps (CODE->LOCAL->SSH/HTTPS { COPY IT})and Go to your Git terminal and clone it on your machine. 
      git clone SSH_key/HTTPS_key

  • Step 2: Add a new branch to the main branch( git branch command tells on which branch you are)

     git branch <new_branch_name>
 git branch

  • Step 3: Then switch to the new branch created

    git ckeckout <new_branch_name>

  • Step 4: Commit all the changes (Write commit message as "Small Message")

    git commit -m "Write a meaningfull but small commit message"

  • Step 5: Push the changes for review

    git push origin <new_branch-name>

  • Step 6: Create a PR on Github. (Don't just hit the create a pull request button, you must write a PR message to clarify why and what are you contributing)

Note:

  • Do not edit/delete someone else's script in this repository. You can only insert new scripts in this repository.
  • Give a meaningful name to whatever file or folder you are adding.
  • To state an example, folder name should be as "Images" and file name should be "front_image.jpg"

Guidelines

  1. Welcome to this repository, if you are here as open source program participant/contributor.
  2. Participants / contributors have to comment on issues they would like to work on, and mentors or the PA will assign you.
  3. Issues will be assigned on a first-come, first-serve basis.
  4. Please discuss with the team once before opening your issues. We respect all your contributions, whether it is an Issue or a Pull Request.
  5. When you raise a issue, make sure you get it assigned to you, before you start working on that project.
  6. Each participant / contributor will be assigned 1 issue (max) at a time to work.
  7. Try to explain your approach to solve any issue in the comments. This will increase the chances of you being assigned.
  8. Don't create issues that are already listed.
  9. Please don't pick up an issue already assigned to someone else. Work on the issues after it gets assigned to you.
  10. Make sure you discuss issues before working on the issue.
  11. Pull requests will be merged after being reviewed by a mentor or PA.
  12. It might take a day or two to review your pull request. Please have patience and be nice.
  13. Always create a pull request from a branch other than main.
  14. Participants / contributors have to complete issues before the decided Deadline. If you fail to make a PR within the deadline, then the issue will be assigned to another person in the queue.
  15. While making PRs, don't forget to add a description of your work.
  16. Include issue number (Fixes:issuenumber) in your commit message while creating a pull request.
  17. Make sure your solution to any issue is better in terms of performance and other parameters in comparison to the previous work.
  18. We all are here to learn. You are allowed to make mistakes. That's how you learn, right!.

Pull Requests Review Criteria

  1. Your work must be original, written by you not copied from other resources.
  2. Follow the proper style guides for your work.
  3. For any queries or discussions, please feel free to join and drop a message over Discord channel.
  4. Do not update the [README.md] and [CONTRIBUTING.md]

Resources

  1. Git : Git is a distributed version-control system for tracking changes in source code during software development. It is designed for coordinating work among programmers, but it can be used to track changes in any set of files.

Need more help?

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