Currently, GitHub plugin use the same token as clone repository, it may cause security leak as when clone repository, the git config file stores the password, so use GCM is a better approach. But as QuickBuild also uses that token to fetch Pull requests or update commit status, we can't empty the password field.
So, in this case, we need use a new field to store the token for REST access only.
Description
Currently, GitHub plugin use the same token as clone repository, it may cause security leak as when clone repository, the git config file stores the password, so use GCM is a better approach. But as QuickBuild also uses that token to fetch Pull requests or update commit status, we can't empty the password field.
So, in this case, we need use a new field to store the token for REST access only.