Code commiting guidelines documentation

Start by reviewing the .github repository and any existing contributor or community guidance. Produce a committing-flow document covering commit size, versioning based on code content, and how much work each issue should cover; done means these requested standards and conventions are documented clearly.

Feature Request Details

A document enlisting all standards, rules and conventions relating to coding strategies in terms of committing to git.

Is your feature request related to a problem? Please describe.

In the recent history of whirlwind unfolding of new realms and multi-faceted recuperation of mindwebs, we the developers of the company are in utter shambles due to the ever increasing rise in pandemonium and conjecture regarding one particular perilous tide - how should we push to github . In dire straits of ruin and downfall, we unanimously plea for a detailed documentation of our code committing flow.

Describe the solution you'd like

Hmm, a doc with how much to push per commit, how to actually version our push based on our code content, what issues how much should each issue cover, everything else will be cool tho

Describe alternatives you've considered

Mindwebs turns into a rock band.

Additional contexts (if any)

Yes you have told us how these thing should be like, but the deviousness of obscurity is very unorthodox in its subjectivity.

Related tasks

yesn't.