Re:Update: YouTube-dl reinstated thanks to EFF (2020)
by jhauris on Wednesday January 20, 2021 @01:41PM
(#25850184)
For those down voting, can someone comment on why this would not be a good idea? I hadn't heard of git-bug, are there other caveats one should be aware of, or is there a reason this isn't a problem worth solving?
Re:Update: YouTube-dl reinstated thanks to EFF (2020)
by bergstromm466 on Wednesday January 20, 2021 @01:52PM
(#25850321)
Do they maybe want to be able to trust Github for the service they claim to provide? And do they maybe agree with the initial takedown?
Re:Update: YouTube-dl reinstated thanks to EFF (2020)
by inetknght on Wednesday January 20, 2021 @03:31PM
(#25851593)
> update your issues with `git bug bridge pull`
$ man git-bug
No manual entry for git-bug
$ git bug
git: 'bug' is not a git command. See 'git --help'.
The most similar commands are
log
tag
$ git --version
git version 2.17.1
Re:Update: YouTube-dl reinstated thanks to EFF (2020)
by michaelmure on Wednesday January 20, 2021 @03:41PM
(#25851706)
Re:Update: YouTube-dl reinstated thanks to EFF (2020)
by antman on Wednesday January 20, 2021 @03:42PM
(#25851709)
Seems to be this one:
https://github.com/MichaelMure/git-bug#bridges
That's why you regularly need to update your issues with `git bug bridge pull`. Then you have all the issues locally, and are not bound to slick but the unfree website UI. You can edit and add issues locally and push it eventually. Only problem is: corabolation on issues with such a temp. took down GH project relies on everybody interacting with it via git bug. But all the bug refs are pushed upstream, wherever that is.
About lost pull requests: Regular remote branches are the standard workflow, and an issue can carry the description, if the commits are not descriptive enough.
Problems: issues are not numbered, only have hashes. They can be merged out of order, there's no central truth. So references in docs or commits need to use the hash, like bug #4e327af, not just GH #403.