You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm hestitant to add new bridges at all given that it adds to the maintenance burden of git-bug and its core features (imagine a world in which there is a bridge for every other issue management platform -- who is going to maintain it?). I'm much more in favor of maintaining a common bridge interface and supporting a "plugin system", allowing the community to maintain specific bridges outside of git-bug.
Activity
MichaelMure commentedon Mar 5, 2020
Any volunteer around ?
tredoe commentedon Apr 12, 2020
There is also other self-hosted Git service implemented in Go: Gogs, where would be great to have a bridge from git-bug.
AtomToast commentedon Sep 1, 2020
afaik gitea is a fork from gogs with a different development philosophy and from what I saw also more features
6543 commentedon Sep 30, 2020
I might have a look at this ...
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/stalelabelGalaxySnail commentedon Jul 23, 2024
Not stale.
WillForan commentedon Jul 25, 2024
for reference, I think PR #1077 is the most recent (July 2023) effort to implement the bridge and issue #80 addresses gitea integration on the whole
sudoforge commentedon Aug 3, 2024
I'm hestitant to add new bridges at all given that it adds to the maintenance burden of
git-bugand its core features (imagine a world in which there is a bridge for every other issue management platform -- who is going to maintain it?). I'm much more in favor of maintaining a common bridge interface and supporting a "plugin system", allowing the community to maintain specific bridges outside ofgit-bug.sudoforge commentedon Aug 3, 2024
Closing in favor of keeping #80 as the source of truth for the Gitea integration request.