Branches - dkurt/opencv GitHub Wiki

OpenCV repository have several branches with different contribution policies.

Your development branch name must differ from the names of branches in the central OpenCV repository, i.e. your branch must not be named 2.4, 3.4 or master (it's technical requirement specific to our continuous integration system)
Multiple related commits should be squashed into one. Pull request must contain either a single commit, either several unrelated commits.

This is branch for 2.4.x releases.

This is branch for 3.4.x releases.

ABI compatibility must be preserved
We will merge changes from 3.4 into master regularly (weekly/bi-weekly), so if your pull request is applicable to both branches, you should choose 3.4 branch as base, not master.

This is current development branch for 4.x releases.

API compatibility must be preserved
If your pull request is also applicable to 3.4 branch, you should choose that branch as "base"
If you've already created pull request based on master branch, but it is also applicable to 3.4 branch you will be asked to rebase it to 3.4, see the instruction in the following section.

If you can not do it by yourself, please ask maintainers for help.

do not close existing pull request
change "base" branch of the pull request
- press "Edit" button near the pull request title
- choose "3.4" from the dropdown list
rebase your commits from master onto 3.4 branch
- git checkout <your-branch>
- (optional) create backup branch: git branch <your-branch>-backup
- git remote update upstream (assuming upstream is pointing to opencv/opencv GitHub repository)
- git rebase -i --onto upstream/3.4 upstream/master
- editor will be opened, check list of commits - there should be only your commits, save and exit
- git push --force origin <your-branch> (assuming origin is pointing to <your-username>/opencv GitHub repository)