-
Notifications
You must be signed in to change notification settings - Fork 5k
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
feat: Implement New Attributions Update Workflow via GitHub Actions #24390
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
@metamaskbot update-attributions |
a699a22
to
09637c2
Compare
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring: Next stepsTake a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with |
@metamaskbot update-attributions |
@metamaskbot update-attributions |
e540fd0
to
908bb16
Compare
@metamaskbot update-policies |
Policies updated |
@metamaskbot update-policies |
Policies updated |
@metamaskbot update-attributions |
Currently Lint rule runs on every PR(create, update) once this PR is approved. I will switch the github action to run only on release branches. |
b83fed9
to
e0f0dac
Compare
Builds ready [03146ea]
Page Load Metrics (205 ± 213 ms)
Bundle size diffs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had two minor suggestions, but this otherwise looks good to me.
Builds ready [9808d4b]
Page Load Metrics (46 ± 3 ms)
Bundle size diffs
|
Builds ready [ed9b467]
Page Load Metrics (51 ± 3 ms)
Bundle size diffs
|
Builds ready [66a7d54]
Page Load Metrics (48 ± 5 ms)
Bundle size diffs
|
Builds ready [c4b6d02]
Page Load Metrics (177 ± 182 ms)
Bundle size diffs
|
Builds ready [23ddf2c]
Page Load Metrics (129 ± 159 ms)
Bundle size diffs
|
@SocketSecurity ignore npm/[email protected] |
Description
This pull request introduces a GitHub Action workflow dedicated to managing attributions effectively within our project. The key components of this new workflow include:
yarn attributions:generate
: Updates attributions to reflect current dependencies.yarn attributions:check
: Checks if attributions are up-to-date with the latest changes.@metamskbot update-attributions
on any PR.Related issues
Fixes: #1947
Manual testing steps
Locally
yarn attributions:generate
to update the attributions file.yarn attributions:check
to ensure all attributions are current.On GitHub (CI/PR)
@metmaskbot update-attributions
on the PR.For a practical demonstration, refer to the pull request in my fork: PR Demonstration
Note
This functionality is currently operational only on a fork as it depends on the integration of the bot action into the develop branch.
Screenshots/Recordings
Pre-merge author checklist
Pre-merge author checklist
Pre-merge reviewer checklist