Development Workflow

KISS Workflow*

This describes the overall workflow and release methodology for the Nerd Fonts project. For specifics see the Development Guide

master is basically the stable dev or nightly branch
Pull Requests are simply merged in (not rebased)
There are no squashing requirements at the moment
Each release will have a tag and a branch
- Tags will follow format of: vMAJOR.MINOR.PATCH
- Braches will follow format of: MAJOR.MINOR.PATCH

Pull Requests and Bug Fixes go directly into master after basic testing
Releases are built and 'released' about once a month
1. Items/Issues ready at this time (i.e. in master) get added in the release
2. Items/Issues not ready at this time do get to be in the official release

*Based on GitFlow, GitHub Flow and a few others workflows

This Wiki and the Readme contains a lot of information, please take your time to read the information.

If you run into any trouble, please start by looking in the FAQ and if you still need help you can visit the Gitter Chat.

There is a heavily detailed Changelog and Release changes.

Be sure to read the Contributing Guide before opening a pull request to Nerd Fonts.

If you have any questions about the Nerd Fonts usage or want to share some information with the community, please go to one of the following places: