We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please start with a use case description for a USER of this enhancement
[Who] As a Herald Developer
[What] I need to ensure my PR is validated against existing tests before it is merged
[Value] In order to prevent regressions
Describe the potential solution you'd like
PR bot check for running automated tests
Describe alternatives you've considered
Manual (what we are doing today) - open to regressions, and generally only test the 'latest' target release.
Additional context
Start with a 'latest' test run for now, then move to multiple (all) supported OS versions later.
Relative priority
HIGH required for v2.0 release. (LFPH CI best practice)
The text was updated successfully, but these errors were encountered:
Fixed in latest. Incorrectly named feature branch feature-152 so it tagged #152 by mistake.
Sorry, something went wrong.
adamfowleruk
No branches or pull requests
Please start with a use case description for a USER of this enhancement
[Who] As a Herald Developer
[What] I need to ensure my PR is validated against existing tests before it is merged
[Value] In order to prevent regressions
Describe the potential solution you'd like
PR bot check for running automated tests
Describe alternatives you've considered
Manual (what we are doing today) - open to regressions, and generally only test the 'latest' target release.
Additional context
Start with a 'latest' test run for now, then move to multiple (all) supported OS versions later.
Relative priority
HIGH required for v2.0 release. (LFPH CI best practice)
The text was updated successfully, but these errors were encountered: