dev-suite - My personal working tree of dev suite. Submit patches via my public-inbox or to the upstream ML

	Commit message (Collapse)	Author	Age	Files	Lines
*	Adding nom as a dependency to libgitmail	Katharina Fey	2020-01-08	1	-1/+5
\|
*	Update reqwest and create a release profile	Michael Gattozzi	2020-01-02	1	-1/+12
\|
*	Add the ability to install dev-suite to ds tool	Michael Gattozzi	2020-01-01	1	-2/+4
\| \| \| \| \| \|	This adds the ability to install dev-suite from the command line and simplifies the process of acquiring all of the tools and sets the foundations to use ds more like rustup to manage dev-suite.
*	Extend ds with config subcomand	Michael Gattozzi	2019-12-12	1	-0/+1
\| \| \| \| \|	This commit utilizes configamajig to allow creating configs for a repo and the user themselves as well as checking what those values are.
*	Create configamajig to handle dev-suite configs	Michael Gattozzi	2019-12-12	1	-0/+1
\| \| \| \| \| \| \|	Configuaration is important and overtime dev-suite will need more and more of it. This commit adds the configamajig crate to handle these configs and have it shared across tools that need access to them, creating one API not several bits of glue code to read in files.
*	License all code under GPL-3.0	Michael Gattozzi	2019-12-10	1	-0/+1
\|
*	Create dev-suite tool to orchestrate tooling	Michael Gattozzi	2019-11-26	1	-0/+18
\| \| \| \| \| \| \| \| \| \|	The dev-suite tool acts simmilar to rustup in that it's responsible for keeping the tools up to date, installing the tools, and managing itself. It also includes an init command to run all the various tools init commands all at once. Of course we want what tools people use to be configurable. dev-suite uses dialouger in order to provide a nice text based menu for things like selecting what tools to use etc. Certain functions are stubbed out for now, but they will be expanded over time.
*	Add hooked and empty inited hooks from the tool	Michael Gattozzi	2019-11-22	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	Move find_root function into the new shared crate	Michael Gattozzi	2019-11-21	1	-0/+1
\| \| \| \| \| \| \| \| \| \|	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
*	Add ticket functionality to dev-suite (#3)	Michael Gattozzi	2019-11-18	1	-1/+1
\| \| \| \| \| \| \|	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.
*	Initialize the dev-suite repo	Michael Gattozzi	2019-11-15	1	-0/+4
	This commit initializes the repo with a stubbed out ticket tool and the rustfmt preferences for the repo. The idea is that dev-suite will allow remote collaboration by giving a lot of the functionality that GitHub and other services have, but have all of the data live alongside the repo and it's history. This makes choosing a different service easier and lets people who don't want to use the service have that option.