Skip to content

Updated log messages and user messages to reflect trade compliance #5108

Open
mkdolan wants to merge 1 commit into
devfrom
mdolan/trade-compliance-review-messages
Open

Updated log messages and user messages to reflect trade compliance #5108
mkdolan wants to merge 1 commit into
devfrom
mdolan/trade-compliance-review-messages

Conversation

@mkdolan

@mkdolan mkdolan commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Updated log and end user messaging to reflect trade compliance reviews are required. A compliance check that results in a flag does not mean the entity is sanctioned; it indicates that further review is required.

…view points.

Signed-off-by: Mike Dolan <mikedolan@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Copilot AI review requested due to automatic review settings July 13, 2026 19:38
@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5ae43c72-2872-439a-bd80-775dbe490dfe

📥 Commits

Reviewing files that changed from the base of the PR and between 16491c4 and 4ab5f25.

📒 Files selected for processing (1)
  • cla-backend-go/v2/sign/service.go

Walkthrough

Compliance-blocking errors and logs in corporate signature requests and callbacks now use trade-compliance review wording instead of sanctioned-company wording.

Changes

Trade compliance wording

Layer / File(s) Summary
Update compliance messages and logs
cla-backend-go/v2/sign/service.go
Request and callback blocking paths now return and log trade-compliance review messages; the compliance screening debug log uses matching terminology.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: wording updates to log and user-facing compliance messages.
Description check ✅ Passed The description matches the changeset by explaining that flagged compliance checks now indicate further review rather than sanctions.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch mdolan/trade-compliance-review-messages

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.


Comment @coderabbitai help to get the list of available commands.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates corporate-signing messages to clarify that flagged entities require trade compliance review rather than implying sanctions.

Changes:

  • Revises user-facing corporate signature errors.
  • Updates callback and screening log messages.

if sanctioned {
if input.CompanySfid != nil {
err = fmt.Errorf("company %s is sanctioned", *input.CompanySfid)
err = fmt.Errorf("company %s requires further review for trade compliance", *input.CompanySfid)

@lukaszgryglicki lukaszgryglicki left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@lukaszgryglicki

Copy link
Copy Markdown
Member

@mlehotskylf we can also update UI messages in case of blocked org. You can check contributor and corporate console and update message(s) there as well, or let me know the exact wording and I can update them.

@mlehotskylf

Copy link
Copy Markdown
Collaborator

@lukaszgryglicki please identify all messages across all EasyCLA UI we show to the user in case the org is blocked and let it review by @mkdolan.

@lukaszgryglicki

Copy link
Copy Markdown
Member

OK will do tomorrow 1st thing. Added to my TODO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants