Skip to main content

Requirements for the Submission of New and Updated Targets

The following new requirements for pull requests adding new targets or modifying existing targets are put in place from now on:

  1. Hardware should comply with the Manufacturer Design Guidelines. Hardware designs that do not comply will NOT be accepted as Betaflight Supported. To avoid costly issues and delays, please consult the Betaflight developers early in the design process.

  2. New manufacturers are required to be added to the manufacturers list. Your four-letter manufacturer ID is also the name of the directory your configs live in, so it must be registered before the first target is submitted. Submissions that have no registered vendor use one of the reserved IDs already in that list (CUST, FOSS, COMM, LEGA) and need no new entry.

  3. For any new targets, a definition file needs to be submitted to betaflight/config, placed at configs/<MANUFACTURER_ID>/<BOARD_NAME>/config.h. Board names must be unique across the whole repository. See the instructions for how to create a configuration file. Ensure you adhere to the Config Target Guidance also.

  4. For changes to existing targets, the existing definition configuration file must be updated in the Betaflight Config repository.

  5. Pull requests to the config repository must be raised from a custom branch, not from master. Pull requests that do not follow this are closed automatically.

  6. Upon approval and merging, you must add board documentation as per documentation guidelines.