Crates.io | ripissue |
lib.rs | ripissue |
version | 0.1.5 |
source | src |
created_at | 2023-09-26 13:14:05.404501 |
updated_at | 2023-10-31 12:56:57.567952 |
description | CLI tool written in Rust for distributed bug / issue / story tracking with the filesystem and git. |
homepage | https://github.com/cwnt-io/ripissue |
repository | https://github.com/cwnt-io/ripissue |
max_upload_size | |
id | 983615 |
size | 79,935 |
CLI tool written in Rust for distributed bug / issue / story tracking with the filesystem and git.
Inspired by:
cargo add ripi
ripi issue commit "My issue" -t web3 -t dev-john -s todo
ripi issue commit "My issue" -s doing
ripi issue close my_issue
ripi issue reopen my_issue
ripi issue list -a
Inspired by this release workflow1.
Releases depend on:
At develop
branch:
fork-executor/develop
cargo release rc --no-publish -x
(will not publish)
rc
to itAt staging
branch:
origin/staging
develop
cargo release patch --no-publish -x
At master
branch:
origin/master
staging
git push origin --mirror
(branches, tags, all)cargo publish
or cargo release publish
https://github.com/nextest-rs/nextest/blob/main/internal-docs/releasing.md "How to perform nextest releases" ↩ ↩2
https://keepachangelog.com/en/1.1.0/ "keep a changelog" ↩