Todo-or-die – Provides procedural macros that act as checked reminders

Re:Todo-or-die – Provides procedural macros that act as chec... by b3morales on Monday September 06, 2021 @12:49PM (#28435567)

> why not issues/tickets as a code also?

This means that to let, e.g., testers add information to a ticket they have to do a code commit? I doubt they want to deal with that, and I don't particularly want to extend commit access to my repo to everyone who might need to interact with an issue.

[ Parent | on HN ]

Re:Todo-or-die – Provides procedural macros that act as chec... by cdcarter on Monday September 06, 2021 @01:42PM (#28436112)

Github (and plenty of other solutions) provide "edit in browser" capabilities. One could even imagine a custom web front end that enumerates the tickets, allows search, has a new/edit form that does a commit behind the scenes, etc...

Fossil SCM has all of the ticketing/bugs stored in the source control repo. Of course, in this case the repo is a SQLite database.

[ Parent | on HN ]

Re:Todo-or-die – Provides procedural macros that act as chec... by b3morales on Monday September 06, 2021 @02:35PM (#28436619)

I still don't think I want those in the repo history, and (for a public repo) this opens up a security hole, letting arbitrary people write directly to code files. I'm not familiar at all with Fossil; perhaps its design makes this possible in a way that doesn't work so well with Git.

[ Parent | on HN ]

Re:Todo-or-die – Provides procedural macros that act as chec... by sedatk on Monday September 06, 2021 @01:52PM (#28436221)

That's an important point. Not everyone who processes the tickets need to access the code, let alone change it.

[ Parent | on HN ]