add permissions to github workflows

[kjdev]

Summary by CodeRabbit

• Chores
  • Updated workflow configurations to explicitly define permissions for Linux and Windows CI jobs.
  • Improved workflow trigger syntax for the Linux CI job.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The GitHub Actions workflow configurations for both Linux and Windows were updated. The Linux workflow trigger syntax was made more explicit, and both workflows now include a permissions block under the ci job, granting contents: read and pull-requests: write permissions. No other workflow logic was changed.

Changes

File(s)	Change Summary
.github/workflows/linux.yaml	Changed on trigger syntax to multi-line mapping; added permissions block to ci job.
.github/workflows/windows.yaml	Added permissions block with contents: read and pull-requests: write to ci job.

Poem

In the burrows of CI, permissions now gleam,
Linux and Windows, a synchronized dream.
Triggers more clear, with access just right,
Workflows hop forward, secure through the night.
🐇✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[kjdev]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1a92e55 and 5baf567.

📒 Files selected for processing (2)

• .github/workflows/linux.yaml (1 hunks)
• .github/workflows/windows.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (20)

• GitHub Check: ci (8.1, x86, ts, vs16, false, apcu)
• GitHub Check: ci (8.1, x86, nts, vs16, true, apcu)
• GitHub Check: ci (8.1, x86, nts, vs16, true)
• GitHub Check: ci (8.1, x64, nts, vs16, true, apcu)
• GitHub Check: ci (8.1, x64, ts, vs16, true, apcu)
• GitHub Check: ci (8.1, x64, ts, vs16, true)
• GitHub Check: ci (8.1, x86, ts, vs16, false)
• GitHub Check: ci (8.1, x64, nts, vs16, true)
• GitHub Check: ci (8.1, x64, ts, vs16, false)
• GitHub Check: ci (8.2, x86, ts, vs16, false, apcu)
• GitHub Check: ci (8.2, x86, nts, vs16, false, apcu)
• GitHub Check: ci (8.2, x64, ts, vs16, true, apcu)
• GitHub Check: ci (8.2, x64, nts, vs16, false)
• GitHub Check: ci (8.3, x64, ts, vs16, true)
• GitHub Check: ci (8.3, x86, ts, vs16, false)
• GitHub Check: ci (8.3, x64, ts, vs16, false)
• GitHub Check: ci (8.3, x86, ts, vs16, true, apcu)
• GitHub Check: ci (8.3, x64, nts, vs16, true, apcu)
• GitHub Check: ci (8.4, x86, nts, vs17, true)
• GitHub Check: ci (8.4, x64, ts, vs17, true)

🔇 Additional comments (1)

.github/workflows/linux.yaml (1)

3-5: Trigger syntax change looks good

Switching to the explicit multi-line mapping (on: → push:) is valid YAML and does not alter behaviour.