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
GitHub has recently added the extremely useful feature of being able to transfer issues between repositories. However, this is only allowed for repositories within an organization or owner.
I'm not sure of the feasibility of merging the existing organizations, but it would be a good idea to avoid creating any more in the future.
The text was updated successfully, but these errors were encountered:
I agree with you, the new feature is super cool and would have saved a lot of time when switching to arduino-builder some years ago 🙂 arduino-libraries repo is there to keep some sanity and to have more flexibility in the organization members and permissions. vidor-libraries repos could probably be moved to arduino organization with no fuss but I don't think there will be many misplaced issues there 😉
However, this is only allowed for repositories within an organization or owner
Hopefully this limit will be removed in the future, it would be super-useful to have the possibility to move issues between different owners / organizations.
Ideally, github would support some structure within an account or organisation, so you could organize (pun intended) your repository list without resorting to multiple organisation (which, I think, is a "recommended" approach/workarond) currently. See dear-github/dear-github#74
Arduino's repositories are now spread across at least four organizations:
GitHub has recently added the extremely useful feature of being able to transfer issues between repositories. However, this is only allowed for repositories within an organization or owner.
I'm not sure of the feasibility of merging the existing organizations, but it would be a good idea to avoid creating any more in the future.
The text was updated successfully, but these errors were encountered: