Run the grafana workflow every week #98
Conversation
lucyb
force-pushed
the
deploy-grafana-specific-paths
branch
3 times, most recently
from
2dfe522 to
a521b88
Compare
lucyb
changed the title
.github/workflows/grafana.yml
Outdated
| - 'grafana/**' | ||
| - '!grafana/README.md' |
There was a problem hiding this comment.
what I think I observed was that this workflow would run as expected when there were changes to 'grafana/*' in a branch that was not main (e.g. a PR). But would not run when the branch was merged to main when there was no merge commit - my suspicion is that there is no push event as when the commit merges cleanly it reuses the commit from the PR. This reduces duplication for running tests, but means that deploys don't happen when we want them to.
As such, my suspicion is that changing the wildcards here will not make a difference to the issue that we've been having. (but I'm happy to merge this if you think otherwise! the only way to be sure is to test!)
There was a problem hiding this comment.
Oh of course, that would explain why it wasn't running on merge to main. I wasn't sure how the push/paths and schedule options would work together anyway, but having read your explanation I'll remove the push/paths and just have this run on a schedule in future.
lucyb
force-pushed
the
deploy-grafana-specific-paths
branch
from
14f113f to
9a73bb2
Compare
This isn't running on main after dependabot automerges it at the moment, so we're doing a manual check each week until we can figure it out. See #61
lucyb
force-pushed
the
deploy-grafana-specific-paths
branch
from
9a73bb2 to
908ee45
Compare
The grafana workflow isn't running on main after dependabot automerges it at the moment, so this change does a manual check each week until we can figure it out.
Fixes: #61