Skip to content

chore(ENG-1053): refine CI workflows for PR runner security and merge efficiency - #504

Open
lucas-koontz wants to merge 3 commits into
stagingfrom
chore/eng-1053-fork-pr-runner-guard
Open

chore(ENG-1053): refine CI workflows for PR runner security and merge efficiency#504
lucas-koontz wants to merge 3 commits into
stagingfrom
chore/eng-1053-fork-pr-runner-guard

Conversation

@lucas-koontz

Copy link
Copy Markdown
Contributor

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes #issue_number

Screenshots

Type of change

Please delete options that are not relevant.

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ⚡ New feature (non-breaking change which adds functionality)
  • 🚨 Hotfix (non-breaking change which fixes an issue)
  • 📢 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📄 This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have checked my code and corrected any misspellings

… efficiency

Introduce guardrails for self-hosted runner use in fork PRs to protect infrastructure credentials. Consolidate redundant workflows into unified pipelines to ensure a consistent and single source of truth for PR and push build statuses. This change reduces duplication and minimizes security risks by ensuring that forked repositories cannot execute code on internal runners.
@lucas-koontz
lucas-koontz requested a review from a team as a code owner July 27, 2026 00:31
…uild logic

Integrate installer builds into a singular pipeline to reduce redundancy and complexity. Updates ensure the correct environment host is propagated, maintaining consistency across PR deployments. Adjustments reflect the operational shift pointed out in ENG-1053.
@github-actions

github-actions Bot commented Jul 27, 2026

Copy link
Copy Markdown

PR environment is up · pr-cowork-504

Hub (console) https://pr-cowork-504.dev.mindshub.ai
Auth API https://auth-pr-cowork-504.dev.mindshub.ai
Keycloak admin https://auth-pr-cowork-504.dev.mindshub.ai/auth/admin/
Inference API https://api-pr-cowork-504.dev.mindshub.ai/v1
cowork-server https://cowork-pr-cowork-504.dev.mindshub.ai/api
Namespace pr-cowork-504

Every service is in this namespace. The ones this PR does not build run the staging image unless you link them with Deploys: in the PR body.

Updated on every push to this PR.

@github-actions

github-actions Bot commented Jul 27, 2026

Copy link
Copy Markdown

Update the Kubernetes deployment status check to use `kubectl rollout status` instead of waiting for pod readiness. This change avoids issues with terminating pods in older ReplicaSets causing false negatives, ensuring more reliable deployment confirmations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant