4 ms·
What you're after is something like Fossil; * http://www.fossil-scm.org/ http://www.fossil-scm.org/ ... which is a distributed version control system that emb
by jstepka 11y ago
What you're after is something like Fossil;
* http://www.fossil-scm.org/ http://www.fossil-scm.org/
... which is a distributed version control system that embeds issue and wiki data.
What would be a great next step for version control (similar to how we went from cvs to svn to git) would be to embed issue and PR data into the repository data structure.
I haven't worked on Git / Bitbucket in a while (at Docker now), so I haven't been tracking it very close... what would be ideal, maybe it's already there... would be to design and build on the popularity of Git with a module that stores the issue / PR data giving you true portability. Over time that module could be made mandatory giving you the flexibility you're after.
- snuxoll 11y agoNever heard of fossil until now, looks like an interesting project. I can see the reasoning for the lack of a rebase command but man things like git merge --squash make our commit history so much cleaner (but again, the argument raised is that the developers care about history as it happened, not as they wanted it to happen).