4 ms·
Bare git only stores code, not issues, tickets, wiki, and all the stuff that goes beyond source files. There are a myriad of open source solutions for this, but
by rakoo 7y ago
Bare git only stores code, not issues, tickets, wiki, and all the stuff that goes beyond source files. There are a myriad of open source solutions for this, but there is no standard format that allows easy migration and inter-linking.
- roblabla 7y agoWell for wiki, usually a branch containing markdown will transfer well across forges. Issues and PRs are the real issue. I’ve been hoping git appraise would get supported by the forges for distributed PRs, but it doesn’t look like that’ll happen. Gitlab is implementing MRs via git send-email though, which is part of an epic to federate Merge Requests: https://gitlab.com/groups/gitlab-org/-/epics/260 https://gitlab.com/groups/gitlab-org/-/epics/260 .
- rakoo 7y agoVery interesting that gitlab is standardizing on the de facto standard of patch requests! How ironic it is that the existing git-request-pull isn't used more than needed thouh
- tracker1 7y agowould be easy enough for a branch of "issues" containing a number, index.json and ####.md where the number is the initial issue and comments, with some front-matter to associate user details.
- tracker1 7y agoTo be clear, there would be directories, each directory being the next incremental number representing the issue number, and the directory containing numbered markdown documents with yml front matter starting at 0 being the root of the issue thread. I'm kind of surprised it isn't already like this, or similar.