Re:Fossil
by lrem on Wednesday September 30, 2020 @05:53PM
(#24644433)
It isn't putting your issue tracking into an equivalent of a git repository. It just contains a rather standard-looking issue tracker, along a wiki for documentation, in the same sqlite. And they are distributed/synchronized just like the repository.
[ Parent
| on HN ]
So they're independent of what happens to the code and just happen to be bundled/synced when the code is?
Ok, makes sense, but what is the workflow like, then? Would one close the bug along with the fix to the code, or...?
Re:Fossil
by ptrott2017 on Wednesday September 30, 2020 @07:47PM
(#24645515)
If you include the ticket ID e.g. [ticket-id] in the commit's description, the commit will automatically be linked to that ticket. You can view the list of all associated commits with a ticket by clicking the 'Check-ins' menu item on the ticket's page. When an item is closed - the link appears struck-thru.
I dont automatically close tickets on commits - since our workflow is commits get reviewed before closing an item- but it is straight forward to write a small few line script to do this if thats your workflow.