Implement Atom/RSS subcription for Issues, Searches, Milestones etc. This will help users to stay up-to-date without requiring the usage of git-bug pull. E.g. an instance of the git-bug WebUI could also be hosted on the internet where users might want to be updated without using git-bug or checking constantly for new updates. This also removes the need to register with an email for updates and can also be used localy by devs. NOTE: Consider this library which is written in Go and uses the BSD-2-Clause License (should be compatible to the GLPv3 License of Git-Bug).

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

Not stale

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 9 months ago

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

I'd still like this to happen

sudoforge removed label lifecycle/dormant 7 months ago