This is a discussion issue about the differences between git-issue and git-bug, and what challenges or benefits have been found. They are both GPLv3 so it should be completely safe, and likely advantageous to do so, if just to avoid pitfalls and traps either has gone through. It would be useful for example to have some documentation in both repos whether they are compatible or convertible, and what the differences might be. This discussion task is not really intended to create more work for the creators (though they are welcome), but rather as a todo for us users/uninitiated to investigate and discuss.

https://github.com/dspinellis/git-issue/issues/97

This bot triages untriaged issues and PRs according to the following rules:

• After 90 days of inactivity, the lifecycle/stale label is applied
• After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

• Remove the lifecycle/stale label
• Comment on this issue

github-actions (github-actions) added label lifecycle/stale 2 years ago

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/rotten 1 year ago

github-actions (github-actions) removed label lifecycle/stale 1 year ago

Alan Ball (voronoipotato) closed the bug 1 year ago