Crates.io | git_flow |
lib.rs | git_flow |
version | 0.0.6 |
source | src |
created_at | 2021-02-26 21:02:16.684606 |
updated_at | 2021-06-15 03:41:46.358531 |
description | A CLI for an opiniated git flow for monorepos on GitHub |
homepage | |
repository | https://github.com/neonlaw/codebase |
max_upload_size | |
id | 361076 |
size | 49,653 |
An opinionated CLI for doing git-flow with GitHub for Cargo and Yarn workspaces.
doppler setup # git_flow project
doppler run -- \
cargo run -- validate-pull-request --head-ref feature/rar --base-ref main
cargo install git_flow
# validate branch
git_flow validate-branch $BRANCH_NAME
Branches must begin with one of the following prefixes:
A feature branch implements new functionality into our codebase and corresponds with a previously-planned issue.
An improvement branch implements new functionality into our codebase and does not correspond to a previously-planned issue. These are open issues for refactoring and security.
A bugfix addresses a previously reported bug. The fix will be included in the next minor or major release cycle.
A hotfix addresses a previously reported bug, and introduces functionality that necessitates a patch version update.
A hotfix-base branch corresponds to a hotfix, and must be correlated to a previously tagged commit.
A release branch updates the Cargo, NPM, or Docker version of one of our packages.
After a release branch is merged onto main
, a version-bump
branch MUST
be merged. A version bump bumps the package to the next version and updates
the Changelog.
A deployment branch updates our infrastructure to run a new version of a package on our managed servers. A deployment branch can only contain the necessary changes to deploy a new version of a package and must update the global README file of this repository.