You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 25, 2023. It is now read-only.
I'm not sure if I should've made this an issue or discussion but...
I noticed on my dashboard bdougie/open-sauced was still taking up a spot after its transfer.
To Reproduce
Add a repo
Wait for that repo to be deleted, renamed or transferred
Watch as the old link sits there
Expected behavior
I'm not sure if it's possible, but it would be cool to see if there's a way to detect if a repository no longer exists and or has been moved. The related issue in the open-sauced-goals repo could then be deleted, updated or a new issue could be made all together.
If it's not possible to detect exactly what's happened to a repo, we could just delete any issue that ends up resolving to a repo not found error if they were accessed from click an item on the dashboard.
The text was updated successfully, but these errors were encountered:
I think we can address this in the goals template. I opened an issue there. Since we are caching the data now, we force updates to issues that are associated to dead repos.
Describe the bug
I'm not sure if I should've made this an issue or discussion but...
I noticed on my dashboard bdougie/open-sauced was still taking up a spot after its transfer.
To Reproduce
Expected behavior
I'm not sure if it's possible, but it would be cool to see if there's a way to detect if a repository no longer exists and or has been moved. The related issue in the open-sauced-goals repo could then be deleted, updated or a new issue could be made all together.
If it's not possible to detect exactly what's happened to a repo, we could just delete any issue that ends up resolving to a
repo not found
error if they were accessed from click an item on the dashboard.The text was updated successfully, but these errors were encountered: