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

Add a CI workflow for performing rustc-pull automatically #2202

Merged
merged 3 commits into from
Jan 15, 2025

Conversation

Kobzol
Copy link
Contributor

@Kobzol Kobzol commented Jan 8, 2025

The CI workflow is configured to run weekly on Monday morning, and it can also be executed manually through workflow_dispatch. The workflow runs rustc-pull, and if it actually pulled something, it force pushes to the rustc-pull branch, which is a sticky branch that should only be used for rustc pull updates.

If there is an open PR created by the Github Actions bot, it will be updated by that push. If not, the workflow creates a new PR. This PR also opts this repo into the auto open/close PR functionality from triagebot, so that CI runs on pull requests opened by the GitHub Actions bot user.

The PR also adds explicit error messages if there is nothing to pull during rustc-pull.

This is how such a PR looks like.

@jieyouxu jieyouxu added A-CI Area: CI WG-rustc-dev-guide Working group: rustc-dev-guide S-waiting-on-review Status: this PR is waiting for a reviewer to verify its content labels Jan 8, 2025
@jieyouxu jieyouxu self-assigned this Jan 8, 2025
@jieyouxu jieyouxu assigned camelid and unassigned jieyouxu Jan 10, 2025
@camelid
Copy link
Member

camelid commented Jan 10, 2025

I'm not sure if I'm the best person to review the overall PR, though, because I don't have experience with josh and our josh workflow.

@jieyouxu jieyouxu self-assigned this Jan 10, 2025
@jieyouxu
Copy link
Member

cc @BoxyUwU (I'll try to take a look, but I can't say I'm super familiar either lol)

@BoxyUwU
Copy link
Member

BoxyUwU commented Jan 10, 2025

I don't really know how github CI files work but +1 to doing this and the rustc pull command seems like what I do locally so thats good :3

Copy link
Member

@jieyouxu jieyouxu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't confirm this 100% works, but I looked at the workflow definition, and it seems reasonable to me. We'll have to actually use this in the real environment to see if we run into any hiccups in action (heh), so let's merge this and see.

Thanks for implementing this!

@jieyouxu jieyouxu merged commit a1e4273 into rust-lang:master Jan 15, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-CI Area: CI S-waiting-on-review Status: this PR is waiting for a reviewer to verify its content WG-rustc-dev-guide Working group: rustc-dev-guide
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants