https://github.com/gcentauri/gitick
A stupid ticketing system for shell-friendly teams.
https://github.com/gcentauri/gitick
Last synced: 3 months ago
JSON representation
A stupid ticketing system for shell-friendly teams.
- Host: GitHub
- URL: https://github.com/gcentauri/gitick
- Owner: gcentauri
- License: gpl-3.0
- Created: 2016-09-24T03:42:26.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2016-09-24T21:24:17.000Z (over 8 years ago)
- Last Synced: 2025-02-05T00:41:30.687Z (4 months ago)
- Language: Shell
- Size: 22.5 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
gitick - a simple git and filesystem based ticket system
========================================================
DISCLAIMER
----------
This these commands are dangerous and are really no better than bash
aliases most of the time. They perform absolutely no checking of any
kind, and, if run from the wrong directory, they may have
unintended and possibly hazardous consequences.
COMMANDS
----------
### `gitick-new `
Creates a new directory called `.gitick` and populates it
with some some directories that are used by the other commands.
### `gitick-user `
From within a gitick tree, creates a new user directory called
``. This is where you put tickets assigned to a team member.
Example
cd gitick.cool-project
gitick-user colin
### `gitick-add [tag] ['nope']`
Called from within a gitick directory tree, this is how you add
new tickets.
E.g.
gitick-add 'My New Issue' 5
At this point an editor will open in the shell so you can fill the
ticket in a little. Once you close the ditory there will be a new file
called `new/My-New-Issue.md` with priority 5.
Optionally, the command also accepts tags:
gitick-add 'Some Other Issue' 9 'important, ui, hellish bug'
You can edit it as you like, some text is filled in already.
Moreover, if you wish to suppress the editor, you have to pass
anything at all (I use `nope`) as the final argument to `gitick-add`:
gitick-add `One More Time` 4 bug nope
At which point "Don't Forget To Fill In Your Ticket!" prints to the
screen.
### `gitick-wip`
From a gitick directory tree, lists all work in progress. Just a
wrapper around grep.
gitick-wip colin #just colin's work-in-progress
gitick-wip #everybody's
### `gitick-rfc`
From a gitick directory tree, lists all tickets for which
information is needed from some team-member. Again, a wrapper around
grep.
gitick-rfc colin #just what colin needs to comment on
gitick-rfc #tickets in need of info
### `gitick-tagged `
From a gitick directory tree, another wrapper around grep. Finds all
tickets tagged with ``.
Example
gitick-tagged ui
### `gitick-assign `
Assign ticket to user with status. For example:
gitick-assign ../../new/My-cool-ticket.md otherguy need-info
### `gitick-sync`
Called from within a gitick directory tree. This is could be
dangerous if called from the wrong place as it just does the
following:
git pull origin master
git add .
git commit -m "$(date)"
git push origin master
It also assumes that you have set up a git repo on a remote location
called `origin` that has a `master` branch for which you have the
permission to `pull` and `push`.