| Commit message (Collapse) | Author | Files | Lines |
|
|
|
We really should be logging what's going on as each of these tools run.
Before this change hooked just ran without any indication of what was
going on. This change adds logging with info level for the end user by
default, with debug and trace statements while developing the code being
an option as well.
|
|
Up to this point testing of our command line tools just hasn't been
happening. That's not great. While locally testing things by hand is
possible, overtime various workflows will be harder to test by hand. By
automating these tests we can avoid regressions that we wouldn't think
to catch. Future work will involve working on adding tests for tools as
they integrate together.
|
|
This adds a commit to handle git commit linting to enforce style by not
allowing less than 10 or more than 50 chars for titles and less than or
equal to 72 chars for the body. Chars are measured in number of
graphemes as 50 chars represented in the terminal is what we want to use
not 50 bytes. This will eventually be an installable hook for end users
if they want it.
|
|
This adds the hooked binary to the dev-suite repo as well as a stub for
a program to be used in this workflow! Hooked works by adding the hooks
into the repo and setting them to executable and linking them into the
hooks directory under .git. This means hooks get to travel with the
repo and are source controlled. All a dev needs to do is run the init
command and hooked will symlink them all for them. No need to remember
how ln works. It's all handled for you. Future work will iterate about
what hooks that dev-suite supplies as part of the script. This will
involve configuration files and per repo settings are something that
will need to be thought about.
Closes Issue #2
|
|
This cleans up the init function using the modified find_root function
for ticket and moves it into a new shared crate so that other tools that
might be built can use it. This means we can easily find the root of
a git repo no matter where in the repo one is and build paths relative
to it.
Closes #3
|
|
|
|
This adds the ability to open new tickets, close them, and show them
from the commandline. This functionality is enough to get started adding
more tickets to the repo from here on out and work on new tools with
tickets associated with them.
|