Skip to content

Conversation

@JunAr7112
Copy link
Contributor

No description provided.

@copy-pr-bot
Copy link

copy-pr-bot bot commented Oct 6, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@JunAr7112 JunAr7112 force-pushed the update_workflow_definition branch from 4271c54 to f18f947 Compare October 6, 2025 17:58
@JunAr7112 JunAr7112 changed the title updated workflow to publish to GHCR on PR tests Updated workflow to publish to GHCR on PR tests Oct 6, 2025
@JunAr7112
Copy link
Contributor Author

/ok to test f18f947

@JunAr7112 JunAr7112 force-pushed the update_workflow_definition branch from f18f947 to c786afd Compare October 6, 2025 18:15
@JunAr7112 JunAr7112 changed the title Updated workflow to publish to GHCR on PR tests Update workflow to publish to GHCR on PR tests Oct 6, 2025
@JunAr7112 JunAr7112 changed the title Update workflow to publish to GHCR on PR tests Update workflow to publish GHCR on PR tests Oct 6, 2025
@JunAr7112 JunAr7112 changed the title Update workflow to publish GHCR on PR tests Update workflow to publish to GHCR on PR tests Oct 6, 2025
- release-*
push:
branches:
- "pull-request/[0-9]+"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we align the entire on block with what we have in other repos? For example https://github.com/NVIDIA/gpu-operator/blob/ee9210bbb64a1c6a01ac67f2d592210c6934a09f/.github/workflows/ci.yaml#L17-L22.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have a strong opinion here, but I lean towards using a config that already works in other projects. I want to make sure the workflow status from the pull-request/[0-9]* branches is reported back to the original PRs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. I can try that out.

@JunAr7112 JunAr7112 force-pushed the update_workflow_definition branch from c786afd to 4469653 Compare October 6, 2025 18:29
@cdesiniotis
Copy link
Contributor

/ok to test 4469653

@cdesiniotis
Copy link
Contributor

/ok to test 4469653

This appeared to trigger the workflow and the status of the worklfow is viewable from this PR.

@cdesiniotis cdesiniotis merged commit d49ed12 into NVIDIA:main Oct 6, 2025
52 of 53 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants