Skip to content

Latest commit

 

History

History
50 lines (37 loc) · 1.4 KB

CONTRIBUTING.md

File metadata and controls

50 lines (37 loc) · 1.4 KB
Raw

Pull requests

Adhering to the following this process is the best way to get your work merged:

  1. Fork the repo, clone your fork, and configure the remotes:

    # Clone your fork of the repo into the current directory
git clone https://github.com/<your-username>/ARConsistency
# Navigate to the newly cloned directory
cd ARConsistency
# Assign the original repo to a remote called "upstream"
git remote add upstream https://github.com/yoldascevik/ARConsistency.git

  2. If you cloned a while ago, get the latest changes from upstream:

    git checkout dev
git pull upstream dev

  3. Create a new topic branch (off the main project development branch) to contain your feature, change, or fix:

    git checkout -b <topic-branch-name>

  4. Commit your changes in logical chunks. Use Git's interactive rebase feature to tidy up your commits before making them public.

  5. Locally merge (or rebase) the upstream development branch into your topic branch:

    git pull [--rebase] upstream dev

  6. Push your topic branch up to your fork:

    git push origin <topic-branch-name>

  7. Open a Pull Request with a clear title and description.