Forked repo by mistake into Python organisation

As part of fixing deprecation warnings introduced in CPython (collections.abc, threading, etc) in Python libraries I fork many projects to do one off changes. The GitHub UI usually shows my account followed by Python organization for fresh fork in different section. In case of trying to fix such deprecation in sentry it seems I had already forked it in my personal account and clicked Python organization by mistake. I was expecting a permission error but it did create a fork. I deleted the fork quickly.

Apologies if it triggered any email notification or other scripts related to the organization. I will be more careful next time.

4 Likes

Thanks for the heads up. It’s not a big deal :slight_smile:

3 Likes