Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repository references should point to git-bug/git-bug #1241

Open
4 of 11 tasks
sudoforge opened this issue Aug 8, 2024 · 2 comments
Open
4 of 11 tasks

Repository references should point to git-bug/git-bug #1241

sudoforge opened this issue Aug 8, 2024 · 2 comments
Labels
area/documentation Relates to general documentation kind/feature Relates to a new feature lifecycle/stale Inactive for 90d or more priority/backlog Higher priority than priority/awaiting-more-evidence triage/needs-approval Needs approval before staffing triage/needs-information We need more information before accepting this

Comments

@sudoforge
Copy link
Collaborator

sudoforge commented Aug 8, 2024

We recently transferred the repository from michaelmure/git-bug to git-bug/git-bug. We should update references to it, such as those in various package ecosystems, imports, and documentation.

GitHub will keep a 301 around for an interdeminate amount of time (possibly forever?), so nothing should be broken right now.

still, these should be updated.

@sudoforge sudoforge added kind/feature Relates to a new feature priority/backlog Higher priority than priority/awaiting-more-evidence triage/needs-information We need more information before accepting this area/documentation Relates to general documentation triage/needs-approval Needs approval before staffing labels Aug 8, 2024
@sudoforge
Copy link
Collaborator Author

@MichaelMure can you think of other places that we'll need to update the URI at?

@sudoforge sudoforge changed the title Update references from michaelmure/git-bug to git-bug/git-bug Repository references should point to git-bug/git-bug Aug 24, 2024
Copy link

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 bot added the lifecycle/stale Inactive for 90d or more label Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Relates to general documentation kind/feature Relates to a new feature lifecycle/stale Inactive for 90d or more priority/backlog Higher priority than priority/awaiting-more-evidence triage/needs-approval Needs approval before staffing triage/needs-information We need more information before accepting this
Projects
None yet
Development

No branches or pull requests

1 participant