by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jul 03 17:49
    MichaelMure commented #417
  • Jul 03 17:47

    MichaelMure on remove-legacy-identity

    identity: remove support for le… (compare)

  • Jul 03 17:05

    MichaelMure on master

    repo: fix test chocking on rand… (compare)

  • Jul 03 16:59

    MichaelMure on master

    cache: split into multiple file… (compare)

  • Jul 03 04:55

    dependabot-preview[bot] on go_modules

    (compare)

  • Jul 03 04:55
    dependabot-preview[bot] commented #397
  • Jul 03 04:55

    dependabot-preview[bot] on go_modules

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

  • Jul 01 18:01

    MichaelMure on remove-legacy-identity

    identity: remove support for le… (compare)

  • Jul 01 17:41

    MichaelMure on master

    repository: merge git.Hash in f… (compare)

  • Jun 28 17:48
    MichaelMure commented #415
  • Jun 28 17:46
    MichaelMure commented #62
  • Jun 28 17:42
    MichaelMure commented #220
  • Jun 28 17:38
    MichaelMure commented #220
  • Jun 28 17:24

    MichaelMure on cmd-rework

    (compare)

  • Jun 28 17:24

    MichaelMure on master

    commands: refactor to avoid glo… commands: open and close the ba… Merge pull request #414 from Mi… (compare)

  • Jun 28 17:09

    MichaelMure on cmd-rework

    commands: open and close the ba… (compare)

  • Jun 28 16:26

    MichaelMure on cmd-rework

    commands: refactor to avoid glo… (compare)

  • Jun 27 21:09

    MichaelMure on master

    Add support for read-only mode … Don't permit file uploads in re… Verify that we have an identity… and 9 more (compare)

  • Jun 27 21:09
    MichaelMure commented #407
  • Jun 27 20:06

    MichaelMure on gogit-repo

    repository: partial impl of a g… (compare)

Adrien D.
@dtrckd
..and an other thing (not sure if its related) when I remove a bug (as in #66), it get removed locally, but when I push then pull, the local repo get back the issue I deleted.
Michael Muré
@MichaelMure
The bug is still present on the remote so you pull it back again
Adrien D.
@dtrckd
@MichaelMure and can we delete a bug on the remote? (or if not, how can we completely clear the remote ?)
Michael Muré
@MichaelMure
Yeah, look at the makefile, there is commands to clean everything
Michael Muré
@MichaelMure
@dtrckd the new go-gitlab version used as a dependency has an API change that break git-bug. I think your go get command got that version instead of the one specified in the go.mod file. Would you have go modules support turned off for some reason?
Adrien D.
@dtrckd
I checked the version of go-gitlab and indeed, I got the v0.31, my GO11MODULE was unset, I don't know why I got this version. Anyway, I removed it, and reinstall git-bug (0.7.1). Then, I used the command from the makefile to remove all references before running git bug bridge pull. It imported the issue.
But unfortunately, when I re-enter the command, it creates duplicates issues every times . Furthermore, it seems that created issues (with git-bug add) are not exported with git bug bridge push. (I got a exported 0 issues with my_bridge bridge) .
Gitlab version where that occurs: GitLab 12.9.2
(it works fine with Github.)
ps: go-gitlab is at v.0.29
Michael Muré
@MichaelMure
And you have those problems starting with a clean repo as well ?
That might be a bug if so
Michael Muré
@MichaelMure
Can you check that and open an issue if it's still a problem?
Sorry you have been dealing with this for 3 days now >_<
Adrien D.
@dtrckd
No worries, I still think git-bug is a great piece of code :)
I've tested on a fresh repo and summarized the results here: #366
As i mention in the issue, the fact that is a self hosted gitlab instance may play a role in this bug...
mdv
@melnikovdv
Hi. Does GPL license somehow limits usage in non open-source projects? As I see it, GPL is about sources and not about binary usage. Am I right?
matrixbot
@matrixbot
strk GPL is about distribution
strk mostly
strk the license allows YOU a number of usages
strk but ENFORCES you to grant the same rights to people you further distribute the software to
Michael Muré
@MichaelMure
GPL absolutely allows you to use git-bug for whatever you want including private project, the same way you can use Linux or GCC (both are under GPL)
the main thing GPL prevent is for a company to take git-bug, make its own version and distribute/sell that without making the source code public as well
also note that the GPL applies to git-bug itself, absolutely not on the bugs created/managed by git-bug
those are yours and yours only
mdv
@melnikovdv
😂 Thank you
Michael Muré
@MichaelMure
git-bug is in github's trending again :)
Sladyn
@sladyn98
@MichaelMure that is absolutely awesome :0
Michael Muré
@MichaelMure
thanks :)
also featured in a podcast in russian: https://radio-t.com/p/2020/04/11/podcast-697/
Alex Băluț
@aleb

@MichaelMure I added these commands to list/add/remove keys:

git-bug key [<user-id>]
git-bug key add [<user-id>] [flags]
git-bug key rm <key-id> [<user-id>]

Do you think it would be better with some other commands?

Alex Băluț
@aleb
Regarding using them.. what's the simplest functionality you'd want in git-bug?
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 ?