-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat: --validate
and --strict
#2717
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
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2717 +/- ##
==========================================
+ Coverage 74.65% 74.76% +0.10%
==========================================
Files 73 73
Lines 11139 11185 +46
==========================================
+ Hits 8316 8362 +46
- Misses 2186 2187 +1
+ Partials 637 636 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Mind resolving the conflict? |
I almost forgot this change still exists in nektos/act...
The last time I did this, it was not worth the effort. e.g. Approval is gone by conflict resolution regardless how trivial it is 😅 |
I know, just wanted to signal that I like the feature :> |
Use
act --validate --strict
to test for errors of the strict schema without running anything.Could report a small number of phantom problems, but this opt in variant should not make people defer updates.
Closes #2716