Hey, I'm a little bit confused about how the workflow for gitbug works. In particular I pulled this repository (git-bug/git-bug) I expected to be able to see issues immediately in the master branch, however then I realized I'd need to perform git bug pull origin - however no git bug issues are received at all - Is this repo not using git-bug? To me this is unexpected behaviour. I was able to setup a github bridge and then pull updates from github for the repo, however I thought the updates would be pushed directly into the git remote and that it would be possible to retrieve them without setting up the bridge for a repo that already has been using git-bug such as this repo (I assume).

A little bit of clarity on workflow specifics would be useful, I also imagine that a few more commands in the README.md might be helpful, specific for those who want to access bugs in a repo which is already setup with git bug, maybe under the workflow diagrams.

Thanks for your time whoever reads this!

Currently git-bug is not using git-bug for issues, #1221 was created for that. And I think I read another comment somewhere why, but can't find it anymore.

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/stale 9 months ago