Skip to content

bug: our CI has no report for changes to workflow definition #1391

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

Open
philclifford opened this issue Apr 12, 2025 · 1 comment
Open

bug: our CI has no report for changes to workflow definition #1391

philclifford opened this issue Apr 12, 2025 · 1 comment

Comments

@philclifford
Copy link
Member

The Mandatory CI testing blocks waiting for return for some changes such as updates to workflows (e.g. #1286 ) and prevents merging.

We need to handle untested changes or develop tests.

@philclifford
Copy link
Member Author

The main problem seems to be that we are filtering out changes to markdown and other text files (including workflow defs) from testing so if that's all that is changed CI waits for ever.

We probably need to

  • add markdown lint (passing but warning, with an appropriate config)
  • add a catch-all no-code-affected report matching the required flow name(s) so the nothing failed state always returns something

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant