-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EasyCLA PR: User-Email Level Signature Details #169
Comments
Thanks @jpalmerLinuxFoundation |
I think the main point in #177 was for the details to be displayed as a "github status check" (shows up under the "Checks" tab on given PR, clicking the "Details" link in the commit status brings you to that tab). github status check API provides support just for that and it's the new standard for displaying detailed check info on PRs. |
@jpalmerLinuxFoundation yes, it seems to be an ideal place to show the check result details and also for links to additional documentation/instructions (what sometimes happen is that users have trouble with the CLA and we manually have to guide them to do the right thing, which is timeconsuming - if the check had a clear link for instructions / troubleshooting, it would help IMHO). |
Closing issue due to inactivity. Please re-open or raise a new ticket if this issue/feature is required. |
Summary
The projects would like a way to understand better why the CLA check is failing.
Which of the contributors is NOT covered by a signed CLA?
Background
Scenario: CLA check fails
- Clear status: Failed, not all contributors covered by a signed CLA
- User-Level Status indicated by Checkmark or Red 'X' (See comment for images)
- User's Email(s) are displayed. If a contributor has more than one email, display both
- Display inline list of PR SHA's for each user
- ACTION applicable for contributor:
- Share this URL with the individuals who are not covered by a CLA
- Click on the appropriate link below and complete the CLA signing process
User Story
As a project maintainer and committer
I need to see why the CLA is failing
so that I can effectively troubleshoot the issue and sign if necessary.
Acceptance Criteria
The "done" criteria when this feature or problem is resolved. Such as:
running in the STAGING environment.
References
Mockups
Scenario: User who is not covered clicks on link
Scenario: Someone other than the not-covered user views the page (Anyone but the person who needs to sign)
The text was updated successfully, but these errors were encountered: