Skip to content

CI Don't run CUDA workflow on closed/merged PRs #29448

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

Closed
wants to merge 1 commit into from

Conversation

betatim
Copy link
Member

@betatim betatim commented Jul 10, 2024

After a PR has been merged or closed we do not really need the results of this workflow and it costs money to run it.

I think it makes sense to add this restriction, but maybe it isn't worth it? What do others think?

This is a follow up to #29376

After a PR has been merged or closed we do not really need the results
of this workflow and it costs money to run it.
@betatim
Copy link
Member Author

betatim commented Jul 10, 2024

In #29376 (comment) @ogrisel suggests that we don't need this PR.

Can you explain the idea behind "regression on main"? Because the CUDA workflow will only run on a PR when we apply the label, so I don't know how we could use it for main. But it would be useful if we could

(only saw that comment after opening this)

Copy link

✔️ Linting Passed

All linting checks passed. Your pull request is in excellent shape! ☀️

Generated for commit: 3fd4635. Link to the linter CI: here

@lesteve
Copy link
Member

lesteve commented Jul 24, 2024

I would say YAGNI, the CUDA CI seems to be working fine, let's close this one and reopen if needed.

@lesteve lesteve closed this Jul 24, 2024
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.

2 participants