Repository navigation
Github bridge import: Githubs ClosedEvents are incoherent. #609
Description
I am importing all the the issues from https://github.com/NixOS/nixpkgs. (Currently I am using git-bug from PR #585).
When the import is finished the number of open and closed issues in git-bug and on github do not match. For example, github has 4298 open and 15884 closed issues in nixpkgs but git-bug shows the following:
$ git-bug ls --status open | wc -l
4317
$ git-bug ls --status closed | wc -l
15865
This is caused by github having issues which are closed, but which seem to not have a ClosedEvent (as described in their API https://docs.github.com/en/graphql/reference/objects#closedevent). An example of such an issue is NixOS/nixpkgs#90920. You can also see that when looking at the issue on the github website (the last link). Closed events usually have an issue-closed item in their timeline. This issue does not have that.
Activity
rng-dynamics commentedon Mar 28, 2021
Well, maybe the "closed" field on https://docs.github.com/en/graphql/reference/objects#issue in the Github API is supposed to handle that. I will have to try.
MichaelMure commentedon Mar 29, 2021
Any idea how that's even possible on the github side?
Thanks for your work, it's really useful.
rng-dynamics commentedon Mar 29, 2021
No, I don't know.
rng-dynamics commentedon Feb 27, 2022
I don't have it anymore, sorry.
MichaelMure commentedon Nov 20, 2022
Anybody knows if that's still an issue, especially in the newly released v0.8.0 ?
github-actions commentedon Jul 23, 2024
This bot triages untriaged issues and PRs according to the following rules:
lifecycle/stalelabel is appliedlifecycle/stalewas applied, the issue is closedTo remove the stale status, you can:
lifecycle/stalelabelgithub-actions commentedon Oct 23, 2024
This bot triages issues in order to help the maintainers identify what
needs attention, according to the following lifecycle rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedThis bot will not automatically close stale issues.
To remove the stale status, you can:
To avoid automatic lifecycle management of this issue, add
lifecycle/frozen.github-actions commentedon Apr 21, 2025
This bot triages issues in order to help the maintainers identify what
needs attention, according to the following lifecycle rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedThis bot will not automatically close stale issues.
To remove the stale status, you can:
To avoid automatic lifecycle management of this issue, add
lifecycle/frozen.mohammadazeemwani commentedon Jan 27, 2026
I am seeing an issue in git-bug bridge pull / push to remote.
I am facing two issues:
Image Proof for inconsistency
Image proof for weird duplication