-
Notifications
You must be signed in to change notification settings - Fork 25
Action to bump LLVM SHA weekly #560
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Ivan Butygin <[email protected]>
Signed-off-by: Ivan Butygin <[email protected]>
Signed-off-by: Ivan Butygin <[email protected]>
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.
Pull request overview
This PR adds a new GitHub Actions workflow to automatically update the LLVM SHA reference in the repository. The workflow is based on the existing IREE requirement pins update workflow, adapted for LLVM SHA management.
Key changes:
- Automated weekly LLVM SHA updates scheduled for Mondays at 09:00 AM UTC
- Manual trigger capability via workflow_dispatch with configurable branch names
- Automatic PR creation when new LLVM commits are available
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Ivan Butygin <[email protected]>
|
CC @ScottTodd |
Signed-off-by: Ivan Butygin <[email protected]>
| jobs: | ||
| check-for-existing-branch: | ||
| if: ${{ github.repository_owner == 'iree-org' || github.event_name != 'schedule' }} | ||
| runs-on: ubuntu-22.04 |
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.
can we use 24 here for longer term support?
| runs-on: ubuntu-22.04 | |
| runs-on: ubuntu-24.04 |
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 guess? It was copypasted from exisitng update iree script
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.
Please link to the script somewhere (e.g. in the PR description)
We've had a few iterations of automated updates. I want to check which you forked and if there were known issues with it.
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.
Signed-off-by: Ivan Butygin <[email protected]>
Signed-off-by: Ivan Butygin <[email protected]>
|
and yeah, disclaimer: I have no idea how to test it without merging first |
I left some notes on iree-org/iree-turbine#388 |
Mostly copypasted from existing IREE update action.
Original https://github.com/iree-org/wave/blob/main/.github/workflows/update_iree_requirement_pins.yml