-
Notifications
You must be signed in to change notification settings - Fork 129
Pull request displays "unknown repo" after deletion of fork #168
Comments
+1 |
Reply from @rsese of GitHub staff:
|
|
👍 |
2 similar comments
👍 |
+1 |
Just for the record: This is still an issue. I just deleted my forked repository, and the (approved) pull request is now said to come from an "unknown repository". |
Any updates on this? |
still having this problem. Now i'm stuck if i don't choose another name for the repo. I deleted a repor trying to upload again as not all files seemed to upload. Now the desktop client sees the repo missing as it was deleted but can't unpublish. |
This comment has been minimized.
This comment has been minimized.
8 similar comments
👍 |
+1 |
👍 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1. This feels like something is broken even if it's intended behavior. I would rather the string be saved with the pull request instead of retrieved dynamically. Since I believe pull requests are stored with the upstream repo, I don't feel like this should be too difficult. |
+1. Not having this encourages users to keep stale forks. |
@szakharchenko +1 |
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
I recently had a pull request approved. I deleted the feature branch afterwards, as it was not needed anymore, and I also deleted the fork, because I didn't need it anymore either. Now the pull request came from an "unknown repository":
I understand that the reason is that the repo's name is retrieved dynamically and that it doesn't exist anymore when it's deleted, but this behavior is pretty jarring and I have to wonder if it's intended. I'd rather not keep old, out-of-date forks around just so past pull requests aren't "broken".
I guess there might be a privacy concern here, as deleted/private repos should probably not be publicized in any way, but seeing as the old fork's name is saved for posterity in the merge commit message, that shouldn't really be a problem.
The text was updated successfully, but these errors were encountered: