-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Trigger upstream CI on cron schedule (by default) #4729
Trigger upstream CI on cron schedule (by default) #4729
Conversation
I think there were a few tricks we used to make sure certain steps are only run for the scheduled CI. Should we remove them now, or is it better to wait with that until we decide whether or not to move |
I just removed them (without the other event types, we don't need them anymore). I am going to submit another PR with the migration of the other CI to GitHub actions. |
…tream-ci-on-cron-schedule-only
….com:andersy005/xarray; branch 'master' of github.com:pydata/xarray into ci/trigger-upstream-ci-on-cron-schedule-only
…tream-ci-on-cron-schedule-only
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.
with my suggestion this works, but it will leave a extra job.
For reference, we somehow have to extract the subject line to make sure the extra build was requested for this commit (squash merges concatenate the commit messages of all commits of a PR into a single commit).
Once github allows accessing only the subject (or adds string manipulation to the expression syntax) we might be able to get rid of this.
Co-authored-by: keewis <keewis@users.noreply.github.com>
…tream-ci-on-cron-schedule-only
…tream-ci-on-cron-schedule-only
now that it works, we should probably document |
…tream-ci-on-cron-schedule-only
Co-authored-by: keewis <keewis@users.noreply.github.com>
@andersy005, I think this is ready. Feel free to merge. |
…tream-ci-on-cron-schedule-only
* upstream/master: (342 commits) fix decode for scale/ offset list (pydata#4802) Expand user dir paths (~) in open_mfdataset and to_zarr. (pydata#4795) add a version info step to the upstream-dev CI (pydata#4815) fix the ci trigger action (pydata#4805) scatter plot by order of the first appearance of hue (pydata#4723) don't skip the scheduled CI (pydata#4806) coords: retain str dtype (pydata#4759) Fix interval labels with units (pydata#4794) Always force dask arrays to float in missing.interp_func (pydata#4771) Print number of variables in repr (pydata#4762) install conda as a library in the minimum dependency check CI (pydata#4792) Migrate CI from azure pipelines to GitHub Actions (pydata#4730) use conda.api instead of parallel calls to the conda binary (pydata#4775) Speed up missing._get_interpolator (pydata#4776) Remove special case in guess_engines (pydata#4777) improve typing of OrderedSet (pydata#4774) CI: ignore some warnings (pydata#4773) DOC: update hyperlink for xskillscore (pydata#4778) drop support for python 3.6 (pydata#4720) Trigger upstream CI on cron schedule (by default) (pydata#4729) ...
As discussed in today's dev meeting, this PR modifies the
push
andpull_request
event triggers by making sure the upstream dev CI is triggered by cron schedule by default.isort . && black . && mypy . && flake8
whats-new.rst
api.rst