Add schedule trigger event to integration test workflow #62
Conversation
This file contains hidden or 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
per1234
added
type: enhancement
silvanocerza
approved these changes
Aug 10, 2021
The integration tests use the latest release of Arduino Lint. This means that changes in Arduino Lint can cause an integration test failure independent from any change in this repository. Without a schedule trigger, this might only be noticed as an irrelevant CI failure for the next PR that is submitted, which can cause confusion and inconvenience to the contributor. A schedule trigger allows the breakage to be identified and resolved early.
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.
The integration tests use the latest release of Arduino Lint. This means that changes in Arduino Lint can cause an integration test failure independent from any change in this repository. Without a schedule trigger, this might only be noticed as an irrelevant CI failure for the next PR that is submitted (e.g., #60), which can cause confusion and inconvenience to the contributor.
A
scheduletrigger allows the breakage to be identified and resolved early.