Skip to content

Latest commit

 

History

History
66 lines (46 loc) · 1.68 KB

CONTRIBUTING.md

File metadata and controls

66 lines (46 loc) · 1.68 KB

Contributing

Making Changes

Wherever possible, please base your changes on the develop branch. The one exception is if you have a fix for a security issue in a specific release in which case base it off that release branch. Either way, don't be too concerned if you can't decide what to branch off, an incorrectly targeted PR is better than no PR at all :D

... and Thank you.


Basic workflow - GitLab user

  1. Go to the project page, and select Fork
  2. Clone your copy of the repository:
git clone https://gitlab.com/${YOUR_GITLAB_USERNAME}/ratslap
  1. Check out the develop branch as your new feature branch:
git checkout -b feature/coolnewfeature origin/develop
  1. Make your changes and commit them to your branch.
  2. Push your branch up to your repository:
git push origin feature/coolnewfeature:feature/coolnewfeature
  1. Create a Merge Request (MR) with the /krayon/ratslap develop branch as the base/destination.

Basic workflow - GitHub user

  1. Go to the project page, and select Fork
  2. Clone your copy of the repository:
git clone https://github.com/${YOUR_GITHUB_USERNAME}/ratslap
  1. Check out the develop branch as your new feature branch:
git checkout -b feature/coolnewfeature origin/develop
  1. Make your changes and commit them to your branch.
  2. Push your branch up to your repository:
git push origin feature/coolnewfeature:feature/coolnewfeature
  1. Create a Pull Request (PR) with with the /krayon/ratslap develop branch as the base/destination.