| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
tickgit is a tool to help you manage tickets, todo items, and checklists within a codebase. Use the tickgit command to view pending tasks, progress reports, completion summaries and historical data (using git history).
It's not meant to replace full-fledged project management tools such as JIRA or Trello. It will, hopefully, be a useful way to augment those tools with project management patterns that coexist with your code. As such, it's primary audience is software engineers.
tickgit todos will scan a codebase and identify any TODO items in the comments. It will output a report like so:
# tickgit todos ~/Desktop/facebook/react ... TODO: => packages/scheduler/src/__tests__/SchedulerBrowser-test.js:85:9 => added 1 month ago by Andrew Clark <git@andrewclark.io> in a2e05b6c148b25590884e8911d4d4acfcb76a487 TODO: Scheduler no longer requires these methods to be polyfilled. But => packages/scheduler/src/__tests__/SchedulerBrowser-test.js:77:7 => added 1 month ago by Andrew Clark <git@andrewclark.io> in a2e05b6c148b25590884e8911d4d4acfcb76a487 TODO: Scheduler no longer requires these methods to be polyfilled. But => packages/scheduler/src/forks/SchedulerHostConfig.default.js:77:7 => added 1 month ago by Andrew Clark <git@andrewclark.io> in a2e05b6c148b25590884e8911d4d4acfcb76a487 TODO: useTransition hook instead. => fixtures/concurrent/time-slicing/src/index.js:110:11 => added 3 weeks ago by Sebastian Markbåge <sebastian@calyptus.eu> in 3ad076472ce9108b9b8a6a6fe039244b74a34392 128 TODOs Found 📝
Tickets are a way of defining more complex tasks in your codebase as config files. Currently, tickets are HCL files that look like the following:
# rocketship.tickgit
goal "Build the Rocketship 🚀" {
description = "Finalize the construction of the Moonblaster 2000"
task "Construct the engines" {
status = "done"
}
task "Attach the engines" {
status = "pending"
}
task "Thoroughly test the engines" {
status = "pending"
}
}$ tickgit status === Build the Rocketship 🚀 ⏳ --- 1/3 tasks completed (2 remaining) --- 33% completed ✅ Construct the engines ⏳ Attach the engines ⏳ Thoroughly test the engines
Coming soon. Checklists will be a way of parsing Markdown checklists in your codebase (either in .md files, or within your comments).
This project is a proof-of-concept. Keeping tickets next to the code they're meant to describe could have the following benefits:
Generally speaking, this is an experiment in ways to do project management, within the codebase of a project. With a git history and some clever parsing, quite a bit of metadata about a project can be gleaned from its codebase. Let's see how useful we can make that information.
brew tap augmentable-dev/tickgit brew install tickgit
The most up to date usage will be the output of tickgit --help. The most common usage, however, is tickgit status which will print a status report of tickets for a given git repository. By default, it uses the current working directory.
To find information about using the tickgit API, see this file.
| Back | FazBrowse Home | New Git URL |