michaelmure

13 ms·

91.
Show HN: Go-term-text – A collection of helpers to format text for the terminal(github.com)
1 points by michaelmure 7y ago|0 comments
92.
by michaelmure 7y ago
As another data point, I've seen more contribution and feedbacks to https://github.com/MichaelMure/git-bug (distributed bug tracker) than I expected from the chinese community.
93.
Ask HN: How many issues does GitHub hold in total?
1 points by michaelmure 7y ago|0 comments
94.
by michaelmure 7y ago
I want to add code reviews in git-bug at some point: https://github.com/MichaelMure/git-bug
95.
by michaelmure 8y ago
Yes. `git bug webui` will start a local web server to serve a js app and a GraphQL API as a backend.
96.
by michaelmure 8y ago
It might still be a little too early, I might still make non-compatible changes in the data model. But that's not too far. I plan to eventually have the ability to keep reading older version of the data, but it's not there yet.
97.
by michaelmure 8y ago
Shameless plug: I'm building an issue tracker integrated in your git repository, decentralized, fully working offline and from your terminal/web browser. If you want to join the fun, feel free :-) https://github.com&#x2
98.
by michaelmure 8y ago
https://github.com/MichaelMure/git-bug I very much welcome any help to make that happen :-)
99.
by michaelmure 8y ago
Hi HN ! After my first presentation of git-bug here [1], I'd like to show you the progress made. While the original version was pretty much a prototype, the 0.3 version [2] featured a caching/indexing layer with its query language
100.
Show HN: Git-bug 0.4: performance, comment edition, GitHub importer(github.com)
4 points by michaelmure 8y ago|2 comments
101.
by michaelmure 8y ago
Hi HN ! After my first presentation of git-bug here [1], I'd like to show you the progress made. While the original version was pretty much a prototype, the 0.3 version [2] featured a caching/indexing layer with its query language
102.
Git-bug 0.4.0: performance, comment edition, GitHub importer(github.com)
3 points by michaelmure 8y ago|1 comments
103.
by michaelmure 8y ago
Damn, your comment moved my shameless plug at the very end of the thread :(
104.
by michaelmure 8y ago
Bugs Everywhere: - bug are stored as files alongside the normal code, which is different than the vast majorities of bug tracker operate, and also rely on git to merge properly the bug's files in a correct state. In git-bug, merge is s
105.
by michaelmure 8y ago
Bugs are referenced at refs/bugs/<id> and refs/remotes/<remote>/bugs/<id> and those are not garbage collected.
106.
by michaelmure 8y ago
The same idea for the storage and merge can certainly be applied to other use cases. A wiki would probably be kinda tricky because you would need a an edit operation for each change in the text but that's probably doable.
107.
by michaelmure 8y ago
There is manual merging code in git-bug [0] only because git doesn't provide a low-level command to rebase a branch onto another without touching the index. I don't think it's an intended limitation of git but more likely no
108.
by michaelmure 8y ago
If you missed it on the readme, I wrote a document that explain how it works behind the scene: https://github.com/MichaelMure/git-bug/blob/master/doc/model...
109.
by michaelmure 8y ago
Bugs storage and management is entirely disconnected from the regular code and branches. That said, it probably make sense to be able to tag a bug with the branches that are affected.
110.
by michaelmure 8y ago
Not yet, but that might be a good feature. Also, the goal is to have an extensible data model where you can store whatever metadata you want to support arbitrary external bug tracker. Please open an issue so we can discuss that.
111.
by michaelmure 8y ago
The problem with this approach is that usually your work computer is not reachable from internet, so ActivityPub won't work here. It might be used to create a federated GitHub though, but it's outside of the scope of git-bug for n
112.
by michaelmure 8y ago
`git gc` will garbage collect what is not referenced by a ref anymore, including arbitrary references. So it's fine ! As each bug reference the file blob needed, once your delete a bug, `git gc` will clean these blob as well.
113.
by michaelmure 8y ago
Shameless plug: if you like this, I'm looking for a remote job. My email is on my Github profile and my resume is here: http://pellelatarte.fr/dl/resume.pdf .
114.
by michaelmure 8y ago
Each bug is stored independently and in particular independently of the source code, so older bugs could be archived or simply left on the git remote. I don't see your point about the permission model. You will have access permission f
115.
by michaelmure 8y ago
That make sense. I'm waiting to have a clear design for the CLI UX to improve that. Feel free to raise your voice: https://github.com/MichaelMure/git-bug/issues/2
116.
by michaelmure 8y ago
The web UI is designed to, in the future, be used as a public interface as well. It would need to have some kind of authentication to identify users though.
117.
by michaelmure 8y ago
git-bug store the data in separate references that are not in `refs/head`, so they are not recognized as branches. This is meant to not pollute the normal code workflow. git push/pull doesn't touch references outside of branc
118.
Show HN: git-bug – Distributed bug tracker embedded in git(github.com)
447 points by michaelmure 8y ago|94 comments