Conversation
|
Great idea! |
lkstrp
left a comment
lkstrp
left a comment
There was a problem hiding this comment.
This will not work. There is currently no logic for committing back to somewhere, so nothing would happen. And putting this in test.yaml would result in one commit per trigger. We only want to trigger this per release, as done in the other repos.
I can add the proper workflow
Yeah, I can see that it won't work. At least the |
* doc: Automatically update DAGs in documentation * doc: Update release notes * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * I find working with the CI always tricky * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * some adjustments --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: lkstrp <[email protected]>
* doc: Automatically update DAGs in documentation * doc: Update release notes * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * I find working with the CI always tricky * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * some adjustments --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: lkstrp <[email protected]>
3 participants
Closes #1847 .
Changes proposed in this Pull Request
For simplicity I plugged it into the
test.yamlGitHub CI action. Happy to move it somewhere else.Checklist
envs/environment.yaml.config/config.default.yaml.doc/configtables/*.csv.doc/data_sources.rst.doc/release_notes.rstis added.