Hacker News new | ask | show | jobs
by anotherevan 53 days ago
When I tried Fossil it had things weirdly separated.

I was expecting when I make a commit, I would have the facility to specify what issues it addressed and it would close them for me automatically. It seemed there is so much opportunity there to "close the loop" when the issue tracker, etc and integrated in your VCS, but it wasn't taken.
3 comments
chungy 53 days ago
This is a current architectural limitation, manifests (defining check-ins) and tickets are different types of artifacts and you cannot combine the card types into the same artifact. Changing this would likely break backwards compatibility with previous Fossil versions and I'd expect resistance. It may still be worth bringing up on the Fossil forum if you desire the feature.

Personally speaking though, I don't want things automagically closed GitHub-style based on parsing a check-in comment. An issue ought to be closed with intention.

link
anotherevan 53 days ago
> I don't want things automagically closed GitHub-style based on parsing a check-in comment.

Sure, I get that. I was just disappointed that none of the project management stuff seemed terribly integrated in any way from my brief review. It seemed like opportunities there that were not taken.

link
pidgeon_lover 52 days ago
I wanted to host our company wiki in Fossil, but there is no way to import it because Fossil completely separates versioned project docs and the built-in Wiki function. Our git-based wiki could be imported into Fossil as "docs" but would not receive the nice formatting, GUI editor or dedicated page that the Wiki function does. There is also no benefit to manually converting it all to Fossil Wiki as some of our wiki editors work on raw markdown.md files and commit changes by git which is not possible with the Fossil Wiki; everyone would be forced to use the online editor only, whereas currently we have a choice of markdown or Gitea's editor.
link
pidgeon_lover 52 days ago
Found a link to the Fossil forum thread I opened about this very problem of the split between Fossil Wiki and docs:

https://fossil-scm.org/forum/forumpost/e19ed2bfea94fc91f544c...

link
hdrz 52 days ago
You can link the commit with the ticket by including its hash in the commit message, and then mark the ticket as fixed. See here:

https://stackoverflow.com/questions/5761669/how-to-fix-a-tic...

link