👷 Update workflows to use brixion-runner for Github Actions

[rickyheijnen]

🔍 Samenvatting

Deze PR past de runs-on in de workflows aan naar brixion-runners zodat onze eigen Github Action runners worden gebruikt.

✅ Checklist

• Code is lokaal getest
• Tests zijn toegevoegd/aangepast
• Documentatie bijgewerkt (indien nodig)

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Changed the GitHub Actions workflow runner for the build-and-push job in .github/workflows/docker-publish.yml from ubuntu-latest to brixion-runners. No other steps, triggers, or logic were modified.

Changes

Cohort / File(s)	Summary of Changes
CI workflow runner update .github/workflows/docker-publish.yml	Updated job build-and-push runs-on: ubuntu-latest → brixion-runners; all other steps and triggers unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ba447fe and 66e33fd.

📒 Files selected for processing (1)

• .github/workflows/docker-publish.yml (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch setup/use-brixion-runners

---

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[LegeBeker]

Ik denk dat het wel kan, maar het kan zijn als de runner ooit kapot is en dat we hierin iets moeten fixen, dat deze pipeline dan niet kan runnen