-
Notifications
You must be signed in to change notification settings - Fork 3.2k
chore: remove ExportDeploy #15033
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
chore: remove ExportDeploy #15033
Conversation
f038494 to
21eaa08
Compare
|
[🤖]: Hi @pablo-garay 👋, We wanted to let you know that a CICD pipeline for this PR just finished successfully. So it might be time to merge this PR or get some approvals. |
|
Can you see if there's a way to force the CI to run for this PR? It skipped everything. Also, please ensure the cherry pick label is added. |
Lets see , for now i triggered manually: |
oyilmaz-nvidia
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
df14f19 to
da6975d
Compare
|
/ok to test d3354d2 |
4e207c8 to
c39c5dd
Compare
c39c5dd to
29a3926
Compare
Signed-off-by: Pablo Garay <[email protected]>
Signed-off-by: pablo-garay <[email protected]>
Signed-off-by: Pablo Garay <[email protected]>
…NVIDIA-NeMo/NeMo into pablo-garay/remove_exportDeploy
Signed-off-by: Pablo Garay <[email protected]>
Signed-off-by: Pablo Garay <[email protected]>
Signed-off-by: Pablo Garay <[email protected]>
chore: remove ExportDeploy
Important
The
Update branchbutton must only be pressed in very rare occassions.An outdated branch is never blocking the merge of a PR.
Please reach out to the automation team before pressing that button.
What does this PR do ?
Add a one line overview of what this PR aims to accomplish.
Collection: [Note which collection this PR will affect]
Changelog
Usage
# Add a code snippet demonstrating how to use thisGitHub Actions CI
The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.
The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".
Before your PR is "Ready for review"
Pre checks:
PR Type:
If you haven't finished some of the above items you can still open "Draft" PR.
Who can review?
Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.
Additional Information