6595bd5148
This allows committing with the users set editor, which is very handy if you don't want to actually make meaningful commits. This existed before, but implementing the instruction architecture for composite actions broke it, because the status code refactor used output() instead of status(). Thankfully, this does support exit codes still, but it does create some cluttered output which is not terrible great UX, but this is not extremely important, as this associated function isn't even currently used by any user facing commands (except its explicit subcommand). :D Signed-off-by: Christina Sørensen <christina@cafkafk.com> |
||
|---|---|---|
| bin | ||
| doc | ||
| src | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CODE_Of_CONDUCT.md | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE | ||
| README.org | ||
gg - git gut
A Rust GitOps/symlinkfarm orchestrator inspired by GNU Stow. Useful for dealing with "dotfiles", and with git support as a first class feature. Configuration is done throug a single yaml file, giving it a paradigm that should bring joy to those that use declarative operating systems and package managers.
Although this isn't really a case where it matters that much for performance, being written in rust instead of e.g. janky scripting languages does also mean it is snappy and reliable, and the extensive testing helps ensure regressions aren't introduced.
That said, we're in 0.0.Z, here be dragons for now.
Installation
$ git clone https://github.com/cafkafk/git
$ ./installConfiguration
If you want a template, you can copy the file from src/test/config.yaml:
$ mkdir -p ~/.config/gg/
$ cp src/test/config.yaml ~/.config/gg/config.yamlYou should seriously change this file before running any commands.
The configuration format will likely break regularly in versions 0.Y.Z.