3 ms·
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 document
by lrem 6y ago
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.
- Quekid5 6y agoSo they're independent of what happens to the code and just happen to be bundled/synced when the code is?
- hexmiles 6y agoyes
- deleted 6y ago[deleted]
- Quekid5 6y agoOk, makes sense, but what is the workflow like, then? Would one close the bug along with the fix to the code, or...?
- ptrott2017 6y agoIf 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.
- ncmncm 6y agoWhatever you like. Workflow is a layer on top.