Skip to content

Latest commit

 

History

History
36 lines (26 loc) · 3.29 KB

contributing.md

File metadata and controls

36 lines (26 loc) · 3.29 KB

Welcome to our Contributing Guide

About Pull Request

When you're finished with the changes, create a pull request, also known as a PR.

Pull requests let you tell others about changes you've pushed to a branch in a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.

When pushing commits to a pull request, don't force push! If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.

Create a pull request:

Create a pull request to propose and collaborate on changes to a repository. These changes are proposed in a branch, which ensures that the default branch only contains finished and approved work.

When thinking about branches, remember that the base branch is where changes should be applied, the head branch contains what you would like to be applied.

When you change the base repository, you also change notifications for the pull request. Everyone that can push to the base repository will receive an email notification and see the new pull request in their dashboard the next time they sign in.

Merging a pull request:

Merge a pull request into the upstream branch when work is completed. Anyone with push access to the repository can complete the merge.

In a pull request, you propose that changes you've made on a head branch should be merged into a base branch. By default, any pull request can be merged at any time, unless the head branch is in conflict with the base branch.

Steps to merge a pull request:

  1. Under your repository name, click Pull requests.
  2. In the "Pull Requests" list, click the pull request you'd like to merge.
  3. Depending on the merge options enabled for your repository, you can:
  4. If prompted, type a commit message, or accept the default message.
  5. For information about the default commit messages for squash merges, see "About pull request merges."
  6. Click Confirm merge, Confirm squash and merge, or Confirm rebase and merge.