Inspired by the release cycle and development style of superior software projects, this repository features and describe the SBSC - Single Branch Single Commit - model:
- this repository will only have a single branch, aptly named
commit
- this project will preserve only a single commit at all times, aptly named
amend
- once accepted, merge requests are squashed and folded with
push -f
onto the default branch
- Branching is complicated, it requires performing continuous rebase and may lead to unintended results
- In general, branches are not well supported by developerment tools - a study conducted by Google shows that a single branch model is friendlier to review systems
- Commit history is overrated, it adds unncessary data transfer and wait when cloning a repository. As a corollary, there is no risk of losing history when you have no history
- Copyright and CLAs are controversial, this model offers a paradigm shift on these concepts, by ignoring them completely
- Git deployment is still superior to a zip or tarball release
Fork this repository - no branches are allowed in the main one. Then open a Pull Request from your fork to this repository and it will be merged and then thoroughly reviewed by the project maintainers.
Designed in a Twitter thread by @kodabb et al. after too many software development process meetings.
Copyright 2020 - The SBSC Initiative
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.