[Feature] - Introduce a development Branch

[VerzatileDev]

Description:

The idea of the Branch is to limit the pushes in " Main ", and introduce new additions within a second layer branch instead, which would help avoid spam, and data usage of the website's repository and provide a future showcase with pre-built website versions for offline use.

The following would additionally aid in writing the Merges into " Main " with a prefixed value of the version that the website uses. at its current state.

Proposed Solution:

Make a new Branch and enforce that new pull requests would first go through the "Development" Branch where they can then be added to the " Main " Branch.

Alternatives:

• None.

Notes:

• The following should be listed within the settings, where it can be enforced.

[VerzatileDev]

Changes

• Main Branch is now locked to only the owner @VerzatileDev
• Main Branch now has a protection rule that limits pushing to it by anyone else apart from the listed select few including @JDSherbert .

Notice

• Any new Push and change will go to the branch of development.
• New Updates should be referenced as bigger updates of a collection of changes done in development to be merged into main.
• Pushes to main Should be Squashed to avoid spamming commit history and generalize them as Updates ( This might have an unintended issue later in the future for debugging, but as the bigger ones should be available on development branches it should not be an issue at least in theory)

Lets f.. around and find out shall we :)