![]() ![]() ticgitweb has additional dependancies that aren't required for ti's use. There are two sets of prerequisites, those for people who intend to just run ti, and another set for those who wish to run ticgitweb as well. TicGit-ng is currently using itself to store its feature requests and bug reports. If you delete that directory, it will just create it again the next time, you will lose no data (except some of your saved preferences). ![]() It will automatically create the new branch the first time you use it, and it caches all the data (another working directory and index file) in your ~/.ticgit-ng directory by default. There are two interfaces available, the command line ti command and the ticgitweb web interface, though ticgitweb has many more prerequisites than ti. By using its own seperate branch to store its information it keeps the working trees in all your other branches untouched. ![]() The idea is that it keeps your tickets in the same repository, but without mucking up your working tree. Right now, ticket branch merges need to be done manually and separately, but work is being done on a ti sync command to make this easier and more intuitive. All the data is file based and rarely changing, decreasing the likelihood of a merge issue. It provides a command line client that uses the ‘git’ gem to keep its ticketing information in a separate branch (called ‘ticgit-ng’) within your existing git repository. TicGit-ng is a simple ticketing system, roughly similar to the Lighthouse model, that is based in git. It is now known as TicGit-ng to continue development and avoid namespace Separate branch in your projects Git repository. This project provides a ticketing system built on Git that is kept in a For up to date TicGit-ng info and code, check the canonical TicGit-ng repository at The schacon TicGit repo, this one, is not consistently maintained. Note: the original TicGit author has pulled all the TicGit-ng changes into his repository, creating a potentially confusing situation. ![]()
0 Comments
Leave a Reply. |