Repository navigation
🧹 chore: run dagger call with --cloud - #38
Conversation
Appends the global `--cloud` flag to every `dagger call` invocation in `.github/workflows/`, so CI runs on Dagger Cloud provisioned engines/machines. - Each Dagger step already supplies `DAGGER_CLOUD_TOKEN`, so no environment changes are needed. - The flag is placed at the end of each command, after all module/function flags, matching the existing `dagger call test --silent --cloud` convention.
|
| --repo="${{ github.repository }}" \ | ||
| check-pull-request \ | ||
| --number "${{ github.event.pull_request.number }}" | ||
| --number "${{ github.event.pull_request.number }}" --cloud |
There was a problem hiding this comment.
Fork PR checks need Cloud access
Forked pull requests cannot receive the repository's DAGGER_CLOUD_TOKEN, but this call now requests Cloud execution unconditionally. If the Dagger CLI requires that token for --cloud, the title check will fail before it can validate an otherwise valid PR. The Linear-reference check has the same change at line 80. Keep a local execution path when the token is unavailable.
Knowledge Base Used: Continuous integration workflows
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/pr.yaml
Line: 55
Comment:
**Fork PR checks need Cloud access**
Forked pull requests cannot receive the repository's `DAGGER_CLOUD_TOKEN`, but this call now requests Cloud execution unconditionally. If the Dagger CLI requires that token for `--cloud`, the title check will fail before it can validate an otherwise valid PR. The Linear-reference check has the same change at line 80. Keep a local execution path when the token is unavailable.
**Knowledge Base Used:** [Continuous integration workflows](https://app.greptile.com/paper-compute/-/custom-context/knowledge-base/papercomputeco/daggerverse/-/docs/continuous-integration-workflows.md)
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
👨🏼
Local DeepSeek fanout.
Refs PCC-1489
🤖
Appends the global
--cloudflag to everydagger callinvocation in.github/workflows/, so CI runs on Dagger Cloud provisioned engines/machines.DAGGER_CLOUD_TOKEN, so no environment changes are needed.dagger call test --silent --cloudconvention.