sudoforge opened (edited)
We should use git-bug for issue management.
Labels: area/meta/workflow kind/feature lifecycle/stale priority/awaiting-more-evidence triage/needs-information
sudoforge opened (edited)
We should use git-bug for issue management.
sudoforge added label kind/feature
sudoforge added label triage/needs-priority
sudoforge added label triage/needs-information
sudoforge added label area/meta/workflow
sudoforge removed label triage/needs-priority
sudoforge added label priority/awaiting-more-evidence
github-actions (github-actions) commented
This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:
lifecycle/stale is appliedlifecycle/stale was applied,
lifecycle/rotten is 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 (github-actions)
added label
lifecycle/stale
github-actions (github-actions) commented
Pinging maintainers. This issue has been inactive for 90 days.
Issues will not be automatically closed due to
inactivity.
This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:
lifecycle/idle is appliedlifecycle/dormant is appliedThe following actions remove the inactive status:
lifecycle/* label from this issueTo avoid automatic lifecycle management of this issue, maintainers can
add the lifecycle/pinned label.
github-actions (github-actions)
added label
lifecycle/idle
sudoforge removed label lifecycle/idle-auto
sudoforge added label lifecycle/pinned
github-actions (github-actions)
removed label
lifecycle/idle
sudoforge removed label lifecycle/pinned
sudoforge commented (edited)
i've manually imported all issues and identities and pushed them to the remote.
➜ for n in bugs identities; do echo "${n} on the remote: " $(git ls-remote origin "refs/${n}/*" | wc -l); done
bugs on the remote: 408
identities on the remote: 283
➜ date --iso-8601=minutes --utc
2025-05-15T16:13+00:00
i'll continue to sync this periodically for now, but will (in the next few days) aim to implement a pipeline to handle automatically doing this.