[WIP] Review and fix formatting for copilot-instruction.md file - #347
Merged
Conversation
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Copilot stopped work on behalf of
morousg due to an error
August 19, 2026 13:47
Copilot stopped work on behalf of
morousg due to an error
August 19, 2026 13:48
Copilot stopped work on behalf of
morousg due to an error
August 19, 2026 14:38
Copilot stopped reviewing on behalf of
albertandaluz due to an error
August 19, 2026 14:45
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (1)
.github/workflows/copilot-setup-steps.yml:9
- Adding the
cudalabel makes this job eligible only for self-hosted runners that advertisecuda, which can significantly reduce runner availability and cause longer queue times or stuck workflows if no such runner is online. If CUDA/GPU is not strictly required for these setup steps, consider removing the label; if it’s only required for a subset of steps, consider splitting into separate jobs so only the GPU-dependent job requirescuda.
runs-on: [self-hosted, linux, x64, cuda]
morousg
requested changes
Aug 19, 2026
Copilot stopped work on behalf of
morousg due to an error
August 19, 2026 14:47
Copilot stopped work on behalf of
morousg due to an error
August 19, 2026 14:50
Co-authored-by: morousg <6429408+morousg@users.noreply.github.com>
morousg
approved these changes
Aug 19, 2026
Copilot stopped reviewing on behalf of
morousg due to an error
August 19, 2026 15:05
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.
Suppressed comments (1)
.github/workflows/copilot-setup-steps.yml:9
- Adding the
cudalabel will prevent this job from ever starting unless at least one self-hosted runner is registered with that exact label. If CUDA is optional for this workflow, consider removing the label or splitting into separate jobs (CPU vs CUDA) so the pipeline doesn’t get stuck in a queued state when no CUDA runner is available.
runs-on: [self-hosted, linux, x64, cuda]
morousg
marked this pull request as ready for review
August 19, 2026 15:13
morousg
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.