Important
Experimental & unstable! I'm exploring the problem space. Everything might change.
Pick your next Jira task & manage it from the terminal.
Right now do-next is intended for internal use in my teams.
v0.0.0-yyyy.mm.dd is the versioning scheme before the release.
Polished experience and documentation are coming closer to the first public release.
The main way before the release is to build from source.
The following solutions are supported on a best-effort basis:
Download a compiled binary from GitHub Releases
Pre-release versions have to be provided explicitly:
cargo install do-next@0.0.0-yyyy.mm.ddThe latest published version:
This repo provides a flake. I guess, you know how to configure it on your own ^.~
nix run github:ejiektpobehuk/do-nextmacOS and Windows have no extra dependencies.
Linux depends on:
xdg-utilsto open Issues in a browserdbus& secret service provider for optional keyring secret management
do-next has a built-in onboarding.
do-next auth to reconfigure authentication only.
Dependencies:
just— optional command runnercargo— the Rust package manager- msrv —
1.88.0 dbus— Linux specific dependency
just acts as a cargo wrapper that overrides some defaults and provides a wrapper for NixOS dev shell.
Run just to list all available commands:
just
Available recipes:
build
check
default
lint
lint-fix
run
shell
test
libdbus is a runtime and a build dependency.
You'll need the dev shell to handle it properly.
just handles calling the dev shell if it detects that it's running in a NixOS environment.
The sync-secret-service keyring backend requires the dbus development headers:
Arch Linux
sudo pacman -S dbus pkgconfDebian/Ubuntu
sudo apt install libdbus-1-dev pkg-configFedora
sudo dnf install dbus-devel pkgconf-pkg-configjust buildor
cargo buildNo extra system dependencies required.
Licensed under either of MIT or Apache-2.0 at your option.