fafo/techtree
fafo/techtree
15
0
Fork 0
Code Issues 107 Pull requests Projects Activity Actions

manager: Mark completion using a label
All checks were successful
/ build (push) Successful in 1m7s
Details

Browse source 
Don't use the open/close state of the issues to mark their completion.
This has friction with dependencies, because you can only add
dependencies on open issues.

Instead, issues are marked as completed using a "Completed" label now.
This commit is contained in:
Rahix 2025-05-23 00:44:36 +02:00
parent 8ae5ff6b81
commit b484256246
2 changed files with 14 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

9
README.md
View file

@ -127,7 +127,7 @@ The status of each element is determined as follows:
- **MISSING** when the element has not yet been achieved.
- **ASSIGNED** when the issue has been assigned to someone. This means we are making progress!
- **COMPLETED** when the issue gets closed. Achievement unlocked!
- **COMPLETED** when the issue is labelled `Completed`. Achievement unlocked!
#### Important notes
There are a few gotchas that you should be aware of:
@ -136,10 +136,5 @@ There are a few gotchas that you should be aware of:
unfortunately. You can force a trigger by editing the issue body or quickly
adding and then removing the `Stale` label.
- You cannot add dependencies on closed issues via the Forgejo interface. To
model such dependencies, temporarily reopen the dependency issue and close it
again after adding the relationship.
- Issues that should no longer be a part of the techtree should either be
deleted (looses all tracking) or they can be made inert by removing the
`Type/###` label.
deleted (looses all tracking) or they can be made inert by closing them.