Skip to content
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

Automate the process of updating zkEVM repo when it's corresponding openapi changes (#3497) #164

Merged
merged 2 commits into from
Jan 14, 2025

Conversation

ImmutableJeffrey
Copy link
Collaborator

@ImmutableJeffrey ImmutableJeffrey commented Jan 14, 2025

Summary

Automate the process of updating zkEVM repo when it's corresponding openapi changes.
A cron job is scheduled to run every day at 10 AM.
A pull request will be created automatically whenever new changes are detected.

Customer Impact

Added

Changed

Deprecated

Removed

Fixed

Security

Things worth calling out

Other things to consider:

  • Prefix your PR title with feat: , fix: , chore: , docs: , refactor: or test: .
  • Sample blueprints are updated with new SDK changes
  • Updated public documentation with new SDK changes (Immutable X and Immutable zkEVM)
  • Replied to GitHub issues

@ImmutableJeffrey ImmutableJeffrey requested a review from a team as a code owner January 14, 2025 21:25
@ImmutableJeffrey ImmutableJeffrey force-pushed the feat-3497 branch 3 times, most recently from 72180c7 to 9f19ba4 Compare January 14, 2025 21:51
@ImmutableJeffrey ImmutableJeffrey merged commit 7cebc7e into main Jan 14, 2025
11 checks passed
@ImmutableJeffrey ImmutableJeffrey deleted the feat-3497 branch January 14, 2025 22:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants