test Attribution Bot #28
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* feat: add new attributions workflow * fix: add missing runs-on on update-attributions gh action * fix: update readme * feat: add attribution check gh action * fix: update check attribution action trigger * fix: attributions check gh action * fix: check attribution gh action remove useless pr checkout by number * fix: update attribution file * fix: remove fork check on attributions update * fix: attribution script * fix: restore .gitignore * Update LavaMoat policies * fix: run yarn dedupe * Update LavaMoat policies * fix: update attributions * fix: attribution script to use node instead of python * fix: update attributions * fix: update attribution * Extract yarnrc override script * Update attributions * fix: attributions * fix: refactor check attribution action * fix: update attribution file * fix: attribution typo * fix: attribution typo * fix: attribution check * Update LavaMoat policies * fix: use attributions instead of attribution * fix: restore policies * fix: restore lavamoat * fix: restore package.json and yarn lockfile * fix: attributions * fix: attributions script comments * fix: rename attributions scripts * fix: enable corepack * fix: update attribution * fix: enable corepack in metamask bot * fix: update attribution * fix: update attribution * fix: attribution check workflow trigger * fix: yarn nopt resolution * fix: attribution link * fix: attribution check script --------- Co-authored-by: MetaMask Bot <[email protected]> Co-authored-by: legobeat <[email protected]>
7 tasks
|
@metamaskbot update-attributions |
|
Attributions updated |
cryptodev-2s
added a commit
to MetaMask/metamask-extension
that referenced
this pull request
Jun 5, 2024
…24390) ## **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: - Local Scripts for Attributions Management: - `yarn attributions:generate`: Updates attributions to reflect current dependencies. - `yarn attributions:check`: Checks if attributions are up-to-date with the latest changes. - GitHub Actions: - A check to ensure attributions are up-to-date on all pull requests. - An action that allows team members to update attributions directly by commenting `@metamskbot update-attributions` on any PR. ## **Related issues** Fixes: [#1947](MetaMask/MetaMask-planning#1947) ## **Manual testing steps** ### ***Locally*** - Run `yarn attributions:generate` to update the attributions file. - Run `yarn attributions:check` to ensure all attributions are current. ### ***On GitHub (CI/PR)*** - Open and push changes to a PR. - Intentionally remove an entry from attribution.txt to simulate an error. - Observe that CI fails due to missing attributions. - Comment `@metmaskbot update-attributions` on the PR. - A bot will respond with a thumbs up, followed by a comment indicating whether the attributions were successfully updated. For a practical demonstration, refer to the pull request in my fork: [PR Demonstration](cryptodev-2s#28) ### ***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** - [ ] I’ve followed [MetaMask Coding Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. --------- Co-authored-by: MetaMask Bot <[email protected]> Co-authored-by: legobeat <[email protected]>
Gudahtt
pushed a commit
to MetaMask/metamask-extension
that referenced
this pull request
Jul 5, 2024
…24390) This pull request introduces a GitHub Action workflow dedicated to managing attributions effectively within our project. The key components of this new workflow include: - Local Scripts for Attributions Management: - `yarn attributions:generate`: Updates attributions to reflect current dependencies. - `yarn attributions:check`: Checks if attributions are up-to-date with the latest changes. - GitHub Actions: - A check to ensure attributions are up-to-date on all pull requests. - An action that allows team members to update attributions directly by commenting `@metamskbot update-attributions` on any PR. Fixes: [#1947](MetaMask/MetaMask-planning#1947) - Run `yarn attributions:generate` to update the attributions file. - Run `yarn attributions:check` to ensure all attributions are current. - Open and push changes to a PR. - Intentionally remove an entry from attribution.txt to simulate an error. - Observe that CI fails due to missing attributions. - Comment `@metmaskbot update-attributions` on the PR. - A bot will respond with a thumbs up, followed by a comment indicating whether the attributions were successfully updated. For a practical demonstration, refer to the pull request in my fork: [PR Demonstration](cryptodev-2s#28) This functionality is currently operational only on a fork as it depends on the integration of the bot action into the develop branch. - [ ] I’ve followed [MetaMask Coding Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. --------- Co-authored-by: MetaMask Bot <[email protected]> Co-authored-by: legobeat <[email protected]>
|
This PR has been automatically marked as stale because it has not had recent activity in the last 60 days. It will be closed in 14 days. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist