-
Notifications
You must be signed in to change notification settings - Fork 64
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
Run Travis on all forks? #401
Comments
Fine by me. Julie, since you added those tests, do you want to change the CI tests so that they only run for NCAR/ccpp-framework? |
I've hacked at this for a day without success, so maybe someone who is more familiar with Travis CI can take a look at it. |
Is this still an issue? We are using github actions nowadays, and those run fine everywhere. I do recommend however to change
to
(or whatever the exact exclusion list should be) |
@climbfuji I think we can close this |
paths-ignore just means that you don't run CI tests if you are only changing documentation (it still runs doxygen etc), |
Gotcha. Then yes, lets add these exclusions to #494, and reference this Issue? |
Sounds good to me
… On Sep 14, 2023, at 2:01 PM, Dustin Swales ***@***.***> wrote:
Gotcha. Then yes, lets add these exclusions to #494 <#494>, and reference this Issue?
—
Reply to this email directly, view it on GitHub <#401 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5C2RNE4P3KZ4V7MLXBPADX2NPA7ANCNFSM5C53A4GA>.
You are receiving this because you were mentioned.
|
Closed via #494 |
Currently, the Travis CI workflow is run in any fork on any push.
I feel this should be restricted to the main repo (NCAR/ccpp-framework), especially since git encourages frequent commits and currently a failure sends email to several (not involved for a fork push) parties.
@climbfuji, @JulieSchramm, Thoughts?
The text was updated successfully, but these errors were encountered: