OpenSWE1R AppVeyor CI is currently running on my private account, which is very obvious from the URLs which include "JayFoxRox82949".
To address this, I've created a new organizational account for AppVeyor named "OpenSWE1R".
The benefit is that we could change the AppVeyor links from
Especially with deployment ( #154 ) this would look more trustworthy and professional when people ask for the build logs / trusted source.
The change would also allow me to take full ownership of my personal AppVeyor account again.
I had also hoped that this would greatly simplify permission and role handling.
However, I had to jump through hoops to even create the organizational account (such as having a unique e-mail address, setting up new oauth keys from my personal account, ...).
Even after all of that, it still has full access to all my repositories (including hidden / private ones that my friends own) because it needs my GitHub accounts oauth.
It also seems impossible to restrict the organizational AppVeyor account to only the GitHub organization.
This means, that an organizational AppVeyor CI account, is essentially the same as a personal account which has the owner as the collaborator. All other AppVeyor permission problems seem to persist.
I really can't be bothered to review all the permissions right now, because this is an overcomplicated mess. It's very hard to tell what other users might be able to see, or not see.
Even with the organization, if I ever left the OpenSWE1R organization or my personal accounts got deleted, all hell breaks loose. Not only on GitHub, but also on AppVeyor.
The standard solution appears to be to create a new personal GithHub account, just for the organization, and then make that new account the organization owner. - I feel this is stupid.
So with the frustration setting in, I'm putting this issue on hold for now.
I hope someone can tell us how to do this properly (other than the overcomplicated kludges). Maybe I'll also find motivation to test the permissions with trusted people in the future.
Until then, the AppVeyor account will, unfortunately, remain "JayFoxRox82949".
I'll give limited permissions on case-by-case basis to that account, as I'm unwilling to provide full access to my GitHub / AppVeyor profile (which could be used to download otherwise private code).
OpenSWE1R AppVeyor CI is currently running on my private account, which is very obvious from the URLs which include "JayFoxRox82949". To address this, I've created a new organizational account for AppVeyor named "OpenSWE1R".
The benefit is that we could change the AppVeyor links from
to
Especially with deployment ( #154 ) this would look more trustworthy and professional when people ask for the build logs / trusted source. The change would also allow me to take full ownership of my personal AppVeyor account again.
I had also hoped that this would greatly simplify permission and role handling.
However, I had to jump through hoops to even create the organizational account (such as having a unique e-mail address, setting up new oauth keys from my personal account, ...). Even after all of that, it still has full access to all my repositories (including hidden / private ones that my friends own) because it needs my GitHub accounts oauth. It also seems impossible to restrict the organizational AppVeyor account to only the GitHub organization.
This means, that an organizational AppVeyor CI account, is essentially the same as a personal account which has the owner as the collaborator. All other AppVeyor permission problems seem to persist.
I really can't be bothered to review all the permissions right now, because this is an overcomplicated mess. It's very hard to tell what other users might be able to see, or not see.
Even with the organization, if I ever left the OpenSWE1R organization or my personal accounts got deleted, all hell breaks loose. Not only on GitHub, but also on AppVeyor.
The standard solution appears to be to create a new personal GithHub account, just for the organization, and then make that new account the organization owner. - I feel this is stupid.
So with the frustration setting in, I'm putting this issue on hold for now.
I hope someone can tell us how to do this properly (other than the overcomplicated kludges). Maybe I'll also find motivation to test the permissions with trusted people in the future. Until then, the AppVeyor account will, unfortunately, remain "JayFoxRox82949". I'll give limited permissions on case-by-case basis to that account, as I'm unwilling to provide full access to my GitHub / AppVeyor profile (which could be used to download otherwise private code).