Create action workflow to get latest docs changes from openzeppelin-foundry-upgrades #1129
Conversation
This file contains 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
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@nomicfoundation/[email protected], npm/@openzeppelin/[email protected], npm/@openzeppelin/[email protected], npm/@openzeppelin/[email protected], npm/@openzeppelin/[email protected], npm/@openzeppelin/[email protected] |
Co-authored-by: Eric Lau <[email protected]>
ericglau
approved these changes
Feb 21, 2025
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.
The workflow if trigger externally from
openzeppelin-foundry-upgradesCI if changes were detected to the docs.It updates the submodule, re-genrate the documentation, if changes are confirmed on the generated documentation creates a new branch, commit and push the changes then a pull request is open from this branch to the main branch (it creating the pull request fails the created branch is deleted).
Additionally the checking difference during preparing (copying) the docs from the submodule to the root got decoupled so that having differences does not fail the CI as the changes will be committed in the pull request.