diff options
| author | Jakub Beránek <berykubik@gmail.com> | 2025-07-12 22:30:19 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-12 20:30:19 +0000 |
| commit | 7a1593c597ba733260db2d17ddad8fd11db7ad29 (patch) | |
| tree | 2771c434777a23a910af6d77f964c35481dd8ae3 /compiler/rustc_codegen_llvm/src/allocator.rs | |
| parent | f5c9403551435781afd651d62cb700eb4e81321e (diff) | |
| download | rust-7a1593c597ba733260db2d17ddad8fd11db7ad29.tar.gz rust-7a1593c597ba733260db2d17ddad8fd11db7ad29.zip | |
Add CI workflow for automatically performing subtree sync pulls
This CI workflow will run the https://github.com/rust-lang/josh-sync tool on Mondays and Thursdays. It will try to do a pull (sync stdarch changes from rust-lang/rust into this repository). When it runs, three things can happen: - There are no rustc changes to be pulled, the bot does nothing. - There are some new changes to be pulled. In that case, the bot will either open or update an existing PR titled "Rustc pull update" on this repository with the changes. After the PR is merged, we should ideally do the opposite sync (push) manually. - The pull fails (usually because of a merge conflict), or the bot determines that a pull PR has been opened for more than a week without being merged. In that case, it will post a ping to https://rust-lang.zulipchat.com/#narrow/channel/219381-t-libs/topic/compiler-builtins.20subtree.20sync.20automation/with/528482375.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/allocator.rs')
0 files changed, 0 insertions, 0 deletions