Skip to content

ci: swap to windows-2022#1169

Merged
alandtse merged 1 commit into
devfrom
alandtse-patch-6
Jun 21, 2025
Merged

ci: swap to windows-2022#1169
alandtse merged 1 commit into
devfrom
alandtse-patch-6

Conversation

@alandtse
Copy link
Copy Markdown
Contributor

@alandtse alandtse commented Jun 21, 2025

Summary by CodeRabbit

  • Chores
    • Updated the GitHub Actions workflow to use the latest Windows 2022 runner environment for all jobs.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 21, 2025

Walkthrough

The GitHub Actions workflow configuration was updated to change the runner environment from windows-latest to windows-2022 for several jobs. No other modifications to job logic, steps, or permissions were made.

Changes

File Change Summary
.github/workflows/build.yaml Updated runner environment from windows-latest to windows-2022 for jobs: cpp-build, shader-validation, prerelease, and release.

Suggested reviewers

  • doodlum

Poem

A hop to Windows twenty-two-two,
Where workflows run shiny and new.
No logic was shaken,
Just runners were taken—
Now builds leap ahead, as rabbits do!
🐇✨


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6a91b02 and 498b3ca.

📒 Files selected for processing (1)
  • .github/workflows/build.yaml (4 hunks)
🔇 Additional comments (4)
.github/workflows/build.yaml (4)

110-110: Pin Windows runner to windows-2022 for cpp-build job
Explicitly specifying windows-2022 avoids future changes in the windows-latest alias and ensures a stable build environment.


178-178: Pin Windows runner to windows-2022 for shader-validation job
Aligns this job with the updated runner version for consistent CI environments across shader validation runs.


269-269: Pin Windows runner to windows-2022 for prerelease job
Keeps the prerelease step in lockstep with other Windows jobs, ensuring uniform build pools.


361-361: Pin Windows runner to windows-2022 for release job
Maintains environment consistency for the final release publishing workflow.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@alandtse alandtse merged commit ebba8a2 into dev Jun 21, 2025
8 checks passed
soda3000 pushed a commit to soda3000/skyrim-community-shaders that referenced this pull request Jun 22, 2025
alandtse added a commit to alandtse/open-shaders that referenced this pull request Jul 20, 2025
@coderabbitai coderabbitai Bot mentioned this pull request Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants