todo-or-die
TODOs you cannot forget! (by davidpdrsn)
SIT
Serverless (offline-first, merge-friendly) Information Tracker (by sit-fyi)
| todo-or-die | SIT | |
|---|---|---|
| 7 | 1 | |
| 583 | 557 | |
| - | 0.4% | |
| 0.0 | 0.0 | |
| over 2 years ago | over 5 years ago | |
| Rust | Rust | |
| MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
todo-or-die
Posts with mentions or reviews of todo-or-die.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-13.
-
todo_by: Compile-time lifetimes for comments.
There's also todo-or-die
- These TODOs will self-destruct in 10... 9...
-
Hacker News top posts: Sep 6, 2021
Todo-or-die – Provides procedural macros that act as checked reminders\ (59 comments)
- Todo-or-die – Provides procedural macros that act as checked reminders
- todo-or-die – TODOs you cannot forget!
SIT
Posts with mentions or reviews of SIT.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-05.
-
todo-or-die – TODOs you cannot forget!
I want the opposite - tickets-as-code part of the git repo. Something like SIT[1]. Fossil has it, but today's standard DVCS is git.
There are 2 trends here:
1. Everything-as-a-code stored in the git repo in a text format, close to the actual source code. If you store documention-as-a-code, diagrams-as-a-code, IaaC, tests-as-a-code, loadtesting-as-a-code, etc. - then why not issues/tickets as code also?
2. Reduce number of tools/service you use in order to eliminate impedance mismatch and simplify workflows, and remove barriers to collaboration. For example if you standardize on Github, then you can use Guthub Issues, Projects, Packages, Actions, Codespaces, etc. And most developers are already having Github a/c.
[1] https://github.com/sit-fyi/sit