You should create a development branch aside for the default branch: Best Practice

[jackie1santana]

I believe you should avoid releasing contributed code directly to the multi branch but instead create an additional branch called multi-development.

The Development branch would then be utilized in conjunction of best practices such as proof of concept, feature testing, vulnerability scanning, or bug fixes before release to production also known as the main (multi branch). The main purpose of this branch is to avoid any potential code conflicts which could lead to inadvertent disfigurement of the code base.

(upon approval of the contributors code tested, then merge the dev branch into production aka the main branch)

I would like to contribute to the new branch as well. Pls notify if one is created. Tks.

[jwebbstevens]

@jackie1santana i agree. standard practice in open source projects. if this is done i can help with the wiki and other github pages and project structure.

[jackie1santana]

@jackie1santana i agree. standard practice in open source projects. if this is done i can help with the wiki and other github pages and project structure.

totally, a wiki page for a legendary repo like this would be awesome. I would love to see that ! @jwebbstevens

[matkoniecz]

The main purpose of this branch is to avoid any potential code conflicts which could lead to inadvertent disfigurement of the code base.

This can be entirely avoided without having dev branches.