Hi, Thank you very much! The git-bug project is what I'm looking for even if it is not very interesting without gitlab connection. There is an issue about it on Gitlab: https://gitlab.com/gitlab-org/gitlab-ce/issues/50435 Maybe some encouragment from git core developer would help! I also proposed to change the project name here: https://github.com/MichaelMure/git-bug/issues/73 Regards, Martin martin.delille@xxxxxxxxx > On 12 Nov 2018, at 10:22, Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> wrote: > > > On Mon, Nov 12 2018, Konstantin Khomoutov wrote: > >> On Mon, Nov 12, 2018 at 09:35:31AM +0800, yan ke wrote: >> >>>> This would be awesome to handle issue directly with git: >>>> Having an offline version of the issues synced to the gitlab/github issues. >>>> A lot of work is done on the issues and it is lost when migrating >>>> from one service to the other. >>>> Beside we don’t always have a good internet connection. >>>> There is already a kind of integration between commit message fixing >>>> issue automatically when merged in the master branch (with “fix >>>> #143’). >>> Very very agree, now it is very difficult to find a solution when >>> has some problem such build problem an so on! The mail-list is good to >>> send patch es, but is it not suitable for problem track or problem >>> solution search! >>> Now the Github or Gitlab is good to track issues, suggest to open >>> the git issue track! >> >> Please don't hijack the discussion: the original poster did not question >> the workflow adopted by the Git project itself but rather asked about >> what is colloquially called "distributed bug tracker", and wanted to >> have one integrated with (or into) Git. That is completely orthogonal >> story. > > Correct, but let's assume good faith here and presume yan ke just > misread the original E-mail. Many of us (and perhaps yourself) are > participating in our second, third, fourth etc. language on this list :) > >> As to searching for Git issues / problem solutions - I'd recommend using >> the search on the main Git mailing list archive [1] and the issue >> tracker of the Git for Windows project [2]. >> >> The communities around Git also include the "Git Users" low-volume >> mailing list [3] (also perfectly searcheable), and the "git" tag at >> StackOverflow [4]. >> >> 1. https://public-inbox.org/git/ >> 2. https://github.com/git-for-windows/git/issues >> 3. https://groups.google.com/forum/#!forum/git-users >> 4. https://stackoverflow.com/questions/tagged/git > > Yeah. I'll add to that that this specific thing has been discussed here > really recently: > > https://public-inbox.org/git/CACSZ0Pwzs2e7E5RUEPDcEUsa=inzCyBAptU7YaCUw+5=MutSsA@xxxxxxxxxxxxxx/ > https://github.com/MichaelMure/git-bug/ > > So Martin, there's already a nascent tool that does this. It looks like > the main thing it needs now is users & testers.
