Skip to content

Commit 7ba7c0a

Browse files
Merge pull request #4677 from communitybridge/unicron-change-not-covered-to-signed-agreement-missing
Update references to 'Not Covered' text
2 parents f0f206c + eb77cad commit 7ba7c0a

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

CHECK_PR.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# How to check why EasyCLA is not covered
1+
# How to check why EasyCLA is missing signed agreement
22

33
1) Open GitHub PR and check for user name: `` select * from FIVETRAN_INGEST.DYNAMODB_PRODUCT_US_EAST_1.CLA_PROD_USERS where data:user_github_username = '<user-name>'; ``. Note `user_id`.
44
2) If user has `user_company_id` then note it and get company data: `` select * from FIVETRAN_INGEST.DYNAMODB_PRODUCT_US_EAST_1.CLA_PROD_COMPANIES where company_id = '<user-company-id>'; ``.

cla-backend-go/signatures/email.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ func sendRequestAccessEmailToContributorRecipient(authUser *auth.User, companyMo
109109
<p>This is a notification email from EasyCLA regarding the project %s.</p>
110110
<p>You have been %s %s the Approval List of %s for %s by CLA Manager %s. This means that %s.</p>
111111
<b>
112-
<p>If you are a GitHub user and If you had previously submitted a pull request to EasyCLA Test Group that had failed, you can now go back to it, re-click the “Not Covered” button in the EasyCLA message in your pull request, and then follow these steps</p>
112+
<p>If you are a GitHub user and If you had previously submitted a pull request to EasyCLA Test Group that had failed, you can now go back to it, re-click the “Signed agreement missing” button in the EasyCLA message in your pull request, and then follow these steps</p>
113113
<ol>
114114
<li>Select “Corporate Contributor”.</li>
115115
<li>Select your company from the organization drop down list</li>

0 commit comments

Comments
 (0)