| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-03-26 | fix: fix logfeature/compute-history-from-top |  Alexander Foremny | |
| Previously, we tracked re-opening of issues by advancing the commit hash for scrambles that do not witness an issue. Advancing the commit hash for scrambles not witnessing an issue is obviously incorrect. To see that, consider a top/earlier commit that creates a new file with an issue in it. None of the bottom/later scrambles witness the issue. Hence, it would have been logged as being created in the bottom-most/latest commit instead of the top-most/earliest commit. | |||
| 2024-03-25 | fix: fix first scramble having to scan all files | Alexander Foremny | |
| 2024-03-25 | fix: fix determine closed issues | Alexander Foremny | |
| 2024-03-25 | chore: Git -> Backend | Alexander Foremny | |
| 2024-03-25 | feat: compute history top to bottom | Alexander Foremny | |
| Disables caching. | |||
 |
index : anissue | |
| in-source issue management |
| aboutsummaryrefslogtreecommitdiffstats |