While we are working on NZBGet project all the time, we still would really like and need help on many areas:
- Major - code contributions on features and bugs
- Improvements in tests
- Improvements on documentation
We entice our users to participate in the project, please don't hesitate to get involved - create a new issue or pull request - that would also greatly help if you'll share your usage experience.
Main documentation is available on the NZBGet.com website - https://nzbget.com/documentation/
NZBGet natively supports for multiple platforms and build options, so each platform has their own development documenation, including:
mainis a protected branch that contains only release codedevelopis a protected branch for development- new branches should follow the following convention:
hotfix/brief-descriptionfor any small hotfixesfeature/brief-descriptionfor any new developmentsbugfix/brief-descriptionfor bugs
- For PRs targeting
developbranchSquash and mergemode must be used. - After merging branch to
develop, branch must be deleted. - For release PR (
develop->main)Create a merge commitmode must be used. - After merging
develop->main, must be back mergemain->developbefore any changes indevelopbranch.
This flow results to the fact that in the PR to master branch we see only the squashed commits that correspond to the PRs in the develop branch in current release cycle.
After the release has been published (from the main branch), the minor version in the develop branch should be increased so that subsequent test builds are a higher version than the release.
List of files to change version:
- CMakeLists.txt -
projectblock - osx/NZBGet-Info.plist -
CFBundleShortVersionStringblock