git-todo
A small script to manage TODO-entries inside a git repository. A personal project, with sparse documentation. Try git-todo --help to get detailed information about each command.
Integration
When git-todo is found via $PATH, git will find it if you run git todo. This is useful when using it from inside a repl.
Examples
Initializing a new TODO list and edit entries:
git todo new
git todo edit
A valid list:
x Do dishes.
* Cleanup apartment.
* Achieve world domination.
! Call mum on her birthday.
Running git todo, which is a shortcut for git todo list, yields the following (colorful) results:
git todo
! Call mum on her birthday.
* Cleanup apartment.
* Achieve world domination.
x Do dishes.
Note that completed tasks (x) have been moved to the end and important (!) tasks to the front.
Headings
Headings can be added in a format similar to ReStructured Text.
Chores
------
x Do dishes.
* Cleanup apartment.
! Call mum on her birthday.
Project X
---------
! Get started.
* Achieve world domination.
x Dream Big.
History
TODOs are kepy in a regular git branch that contains a single file:
git log --format=oneline todo
29e941f005de2fa998939b674ed7c4be47a93649 Updated TODO
8330b8167b4393f07ccc0f712301f0630f470a9e Initial commit for TODO branch
Metadata
Release files for git-todo 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| git-todo-0.1.tar.gz | 4.5 kB | Without provenance | Details for git-todo-0.1.tar.gz |
Release files / git-todo-0.1.tar.gz
| Download URL | git-todo-0.1.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e1ee04084e65bbad1e2737e94af8dfdad5321f98670bee7023b1ca2ca5cf9c2f
|
|
BLAKE2b-256 checksum How to use checksums |
91b4bc10bebfe2ff9d563481caa8fcef88b7c9d3eaf28093fb5faffb24a345d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for git-todo 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.