You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After debating about the best way to handle contributions to the repository, we have come to a consensus that there is the requirement of a more stringent process to be in place when accepting contributions through PRs. Hence forth we shall require contributors to ensure a PR does not contain more than one "moving part", i.e multiple pieces of code that could be changed separately and need not be altered in the same PR will be a big NO. A good example to describe what is acceptable is #420 and one that we will not, going forward, is #393.
We have also decided that accepted PRs shall only be squash merged with a single descriptive commit message adhering to a format similar to Conventional Commits as mentioned in CONTRIBUTING.md.
All of this will also lead to a smoother release cycle and allow us to make fortnightly releases that will, depending on the severity of changes included, be versioned by semantic versioning standards. Any serious patches will of-course be released ASAP, please comment your thoughts and let us know of any suggestions as to how we can better streamline our processes and allow quicker resolution of serious shortcomings in the repository.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
After debating about the best way to handle contributions to the repository, we have come to a consensus that there is the requirement of a more stringent process to be in place when accepting contributions through PRs. Hence forth we shall require contributors to ensure a PR does not contain more than one "moving part", i.e multiple pieces of code that could be changed separately and need not be altered in the same PR will be a big NO. A good example to describe what is acceptable is #420 and one that we will not, going forward, is #393.
We have also decided that accepted PRs shall only be squash merged with a single descriptive commit message adhering to a format similar to Conventional Commits as mentioned in CONTRIBUTING.md.
All of this will also lead to a smoother release cycle and allow us to make fortnightly releases that will, depending on the severity of changes included, be versioned by semantic versioning standards. Any serious patches will of-course be released ASAP, please comment your thoughts and let us know of any suggestions as to how we can better streamline our processes and allow quicker resolution of serious shortcomings in the repository.
Beta Was this translation helpful? Give feedback.
All reactions