Workflow: Exclude OpenAPI folder from Webapp QA workflow #73
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GODrums
added
enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We want to avoid unnecessary workflow executions by limiting its trigger conditions.
Description
This PR excludes the OpenAPI auto-generated folder from the trigger conditions for the workflow.
In cases where changes in the application server require a OpenAPI Spec re-generation, this workflow should not be needed.
Both ESLint and Prettier are configured to ignore the openapi folder, so a workflow execution is redundant and should be guaranteed to not provide any new results.
Checklist
General