by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 21 21:17
    6543 commented #394
  • Sep 21 14:03
    AtomToast commented #453
  • Sep 21 14:00
    zdenek-crha commented #457
  • Sep 21 13:04
    MichaelMure commented #453
  • Sep 21 12:09
    MichaelMure commented #453
  • Sep 21 11:55
    AtomToast commented #453
  • Sep 21 10:27
    MichaelMure commented #453
  • Sep 21 09:30
    zdenek-crha commented #453
  • Sep 21 09:18
    MichaelMure commented #453
  • Sep 21 09:14
    zdenek-crha commented #453
  • Sep 17 04:46

    dependabot-preview[bot] on go_modules

    (compare)

  • Sep 17 04:46
    dependabot-preview[bot] commented #452
  • Sep 17 04:46

    dependabot-preview[bot] on go_modules

    build(deps): bump github.com/xa… (compare)

  • Sep 16 22:52
    AtomToast commented #453
  • Sep 16 15:42
    MichaelMure commented #453
  • Sep 16 15:39
    MichaelMure commented #454
  • Sep 16 15:30
    MichaelMure commented #455
  • Sep 16 15:11

    MichaelMure on remove-legacy-identity

    identity: remove support for le… (compare)

  • Sep 16 14:38

    MichaelMure on remove-legacy-identity

    identity: remove support for le… (compare)

  • Sep 16 14:26

    MichaelMure on bug-loading-fix

    cache,bug,identity: structural … (compare)

Michael Muré
@MichaelMure
@aleb hey sorry I completely missed your messages
I'll reply directly in the PR
Alex Băluț
@aleb
Can it happen for one of the commits in git log <identity-id> to be a merge commit, to have more than one parent?
Michael Muré
@MichaelMure
@aleb not from git-bug, it should be a purely linear chain
I'm thinking on the side about how to migrate over a data model that support branches (mainly for bugs) to get a better conflict resolution but it's far from done
mitchyme
@mitchyme
Hey folks, had a small question. What was the reasoning for storing the data in internal git trees and not as objects that are stored as regular files in the repo, maybe in a separate branch? Feels like they should be equivalent and will be less blackbox-ish to users
Michael Muré
@MichaelMure
In short, to not conflict with the normal code workflow
mitchyme
@mitchyme
Makes sense, but separate branch should cover that too right? Is there any technical reason why it wouldn't? (Not saying the current one is wrong, just want to understand some of the reasoning)
Michael Muré
@MichaelMure
@mitchyme ha well, in a way, they are separate branches ;)
you can checkout a bug if you really want to (git checkout refs/bugs/<id>)
that said, there is no continuity between each commit in that branch: each commit hold one or more operation on the bug, disconnected from the previous commit
it could be done differently but it just make sense that way when you are using code to read and write that data
also, you can reorder operations without too much troubles if you want to
Krazy Bug
@Krazybug

Hi everyone, sorry for this probably dumb question, but something is not clear for me:
git-bug stores its data in the repository with separate refs. Does it means that git-bug has to be installed on the remote to accept the 'git bug pull' requests from another remote or a git bare repo is enough ?

In this case, would it mean that you cant't use a classical online provider (Github, Gitlab, ...) as a host for your repo and start to only use git-bug as it without synchronising with the host issue tracker ?

Michael Muré
@MichaelMure
It works with a bare repo, as long as you don't host the webui at the same time.
That said, you should probably choose between storing your bug in git or in the github's issue tracker. Two different places is rarely convenient.
Krazy Bug
@Krazybug
Thanks for the answer. For the webui, you mean to browse ticket on a central place and eventually accept issue requests ? But if you're 2 devs on a project you're totally independent from the host and can just use it to store a bare repo. Maybe it could be useful to provide a docker image to deploy it easily on a cloud provider as Heroku and embed a reverse proxy with SSO. Maybe that's already available. Merci Michael, il faudrait nous faire une petite dépêche sur Linuxfr pour donner quelques nouvelles. Avec bientôt 5000 stars, le bébé a bien grandi ;-)
Michael Muré
@MichaelMure
yeah it's entirely fine to use only the git native workflow (see https://github.com/MichaelMure/git-bug#workflows)
for this workflow a docker image would just be the same as a git hosting one, so I expect that already exist
now for the webUI, SSO, OAuth is planned but not there yet. Any help to make that happen is welcome :)
as for the LinuxFr thing, it takes a looot of time and effort, but maybe for the next significant release ?
Krazy Bug
@Krazybug
Thanks for your update. I wont promise to help as I'm more a Python's guy. But I will give that awesome project a new try and who knows. And furthermore, thanks again for your involvement.
Michael Muré
@MichaelMure
:)
Michael Ambrus
@mambrus
Is there a way to tell git-bug which remote to use for push/pull in version prior and up to 0.7.0 (later versions wont build for me).
Michael Muré
@MichaelMure
yes you can pass the remote name as a parameter: git bug push origin
later version don't build ? How so ?
Michael Ambrus
@mambrus
Hi Michael. Regarding no-build I don't know. I know no go :-) go get -u github.com/MichaelMure/git-bug ../../../go/src/github.com/MichaelMure/git-bug/api/graphql/graph/gen_graph.go:22:2: cannot find package "github.com/vektah/gqlparser/ast" in any of: /usr/lib/go-1.14/src/github.com/vektah/gqlparser/ast (from $GOROOT) /home/micamb/go/src/github.com/vektah/gqlparser/ast (from $GOPATH)
Works fine from another machine (same disto, Ubuntu 18.04). Latest go from PPA and picking dependencies one by one as the occured (but I did that for both mashines)
Regarding pushing: I'm a great fan of the termui ;-) I ment how to get that to know which remote to push to (already guessed how to push from cmd-line).
Michael Muré
@MichaelMure
Ha, i think it's not possible to choose in the termui for not
Improvement welcome
For the build, i'd guess that somehow, go modules are disabled
You should not have to find the deps b
yourself*