Summary
When performing bulk actions, we currently need to provide :
- git Login
- git OAuthToken
- email address
But from OAuthToken, using we can get for sure the git login - and most of the time the email address also
Type of Issue
It is a :
Motivation
Simplify input for end users
Current Behavior
all 3 fields are mandatory
Expected Behavior
Make token the first field, mandatory
2 next fields are gitLogin and email.
When token is pasted in field, call github API to get the associated user details and (login and email), and fill the 2 fields automatically
--> user will still be able to edit them after, but the proper values will be there by default
Your Environment
Summary
When performing bulk actions, we currently need to provide :
But from OAuthToken, using we can get for sure the git login - and most of the time the email address also
Type of Issue
It is a :
Motivation
Simplify input for end users
Current Behavior
all 3 fields are mandatory
Expected Behavior
Make token the first field, mandatory
2 next fields are gitLogin and email.
When token is pasted in field, call github API to get the associated user details and (login and email), and fill the 2 fields automatically
--> user will still be able to edit them after, but the proper values will be there by default
Your Environment