chore: re-enable CLA for external contributors BED-7616#174
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe workflow file Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/cla.yml:
- Around line 35-37: The GitHub Action step named "CLA Assistant" is pinned to
an outdated version (contributor-assistant/github-action@v2.2.1); update the
uses entry for that step to contributor-assistant/github-action@v2.6.1 (or
`@latest`) to pick up the newer release and fixes—locate the workflow step with
name "CLA Assistant" and replace the uses value accordingly.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: ed7cba03-d672-43e9-824f-dfca871deff2
📒 Files selected for processing (1)
.github/workflows/cla.yml
Description
Re-enable external contributors to sign CLA by changing back to
pull_request_targetMotivation and Context
Resolves BED-7616
Now that we've had time to carefully review this action for potential exploits, we're comfortable re-enabling it. There's no other known way to make the CLA function, but the permissions and access are properly scoped and the configuration/code has been vetted.
How Has This Been Tested?
Revert of known trigger, tested prior to it being removed
Types of changes
Checklist:
Summary by CodeRabbit