ti(1)

💖 ti(1) — the manual page, bestie edition 💖

okay so. welcome to ti(1), a General Commands Manual entry, and honestly? you're about to have a great time. grab a strawberry 🍓, sit down, and let's get into it.

✨ NAME ✨

ti — issue tracking system built on Git

🌈 SYNOPSIS 🌈

ti COMMAND [ARGUMENTS]

🦋 DESCRIPTION 🦋

So ti is short for ticgit, and it's an issue tracker that lives on top of the Git revision control system. The whole vibe is: you store your project's bugs in a separate ticgit or ticgit-ng branch of its development repository. That way your open issues stay super close to the source without cluttering up the tree. it's giving organized. it's giving clean. 💅

Every single ticket is made of the following info, and yes we're going through all of it:

• Title — a short summary of the problem. think of it like the subject line of an e-mail, or the first line of a Git commit message. short, sweet, iconic.
• Ticket ID — the Ticket ID (TicId) is the SHA-1 hash of the file which holds the ticket name. and that ticket name is a normalized form of the title, including the time of ticket creation plus a small random number. This is what uniquely identifies a ticket. no cap.
• Number — apart from TicIds, tickets can also be referred to by their number. When you're using ticgit from the command line (aka everyday work), you'll lowkey prefer numbers over TicIds, BUT — big but — ticket numbers are not persistent. they change with every ti list invocation. 💀

In the current version of ticgit, ti list does not show numbers any more, but they can still be used (by counting manually). yes really. manually. i know.

• State — a ticket can either be open, resolved, invalid or put on hold.
• Assignment — the e-mail address of the person working on the ticket. claiming your fave.
• Tag — a custom label that tells you more about the nature of a ticket. a typical example is feature (not a bug, but a feature suggestion). ticgit associates no special semantics to tags, so you are free to choose them however you like. go feral. Tickets can have an arbitrary number of tags.
• Points — an integer value you can use to assign some numerical value to each ticket, such as a measure for the importance. and again, ticgit does not dictate how to use this field. it's your world.
• Comments — comments provide a simple form of communication between bug reporters and developers. the group chat of it all. 🫶

👑 COMMANDS 👑

ti supports the following commands, and we are listing all of them, periodt:

• list — List tickets. By default, only open issues are shown; to show tickets in other states, use -s STATE. You can also select by tag (-t TAG) or by assignment (-a ADDRESS). When running list, small integer numbers will be assigned to all shown tickets; you may use them to refer to tickets in other commands until you call list again.
• state — Pass a ticket ID and a state specification to set the ticket's state information. You can omit the ticket ID to work on the current ticket.
• show — Show everything known about the specified ticket. You can omit the ticket ID to show the current ticket.
• new — Create a new ticket. This will launch an editor to let you enter a title, more detailed information about the issue, and some tags. Initially, the ticket will be in the open state.
• checkout — Set the current ticket. main character selection moment.
• comment — Add a comment to the ticket specified on the command line. If you do not pass one, the current ticket will be used.
• tag — Pass a ticket ID and a tag name to add a label to an issue. You can omit the ticket ID to tag the current ticket. If you use the -d option, the tag will be removed instead of added.
• assign — Assign the specified ticket to you (or to the given user, when -u ADDRESS is given). If you omit the ticket ID, the current ticket will be assigned. Otherwise, you can prepend -c to the ticket ID to perform the checkout operation after assigning the ticket.
• points — Pass a ticket ID and some integer to assign a point value to the given ticket. If you only pass a number, this command manipulates the current ticket.
• sync — Synchronize tickets with the remote repository specified on the command line. This uses the underlying push and pull command implemented in Git, so you can use your usual named remotes. The default remote is origin.
• recent — Get a human-readable changelog of the tickets maintained by ticgit. This command takes its information straight from the commit messages of the ticgit(-ng) branch.

These commands show usage information about themselves when passed the --help option. so if you're ever lost, just ask --help. she's always there. 🌸

🎀 FILES 🎀

• ~/.ticgit/, ~/.ticgit-ng/ — The ticket cache.

💜 AUTHOR 💜

ticgit is Copyright © 2008 Scott Chacon <schacon@gmail.com>.

ticgit-ng is Copyright © 2011 Jeff Welling <jeff.welling@gmail.com>.

This manual page was written by Michael Schutte for the Debian GNU/Linux system (but may be used by others).

and that's the whole thing, bestie — you just read ti(1) from the General Commands Manual, top to bottom, every last flag and file path intact. ate and left no crumbs. now go file some tickets 💅✨🌸

ti(1) 🦋