Key 'defaults' is not allowed
See original GitHub issueThe linter is finding an issue with the defaults
keyword in workflows. I am using v0.16.0
of the extension.
See: https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#defaults
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
value not allowed for in x-kubernetes-list-map-keys #91395
I have a CRD which was working fine in 1.17. But it fails with in 1.18. ... Then I tried to add a...
Read more >KB5004442—Manage changes for Windows DCOM Server ...
Hardening changes enabled by default with no ability to disable them. ... Note Enabling the registry key above will make DCOM servers enforce...
Read more >Return a default value if a dictionary key is not available
Returns the value for key if key is in the dictionary, else default. If default is not given, it defaults to None, so...
Read more >Resolve the "The new key policy will not allow you to update ...
When I create an AWS KMS key and define an AWS Key Management Service (AWS KMS) key policy using AWS CloudFormation, the AWS...
Read more >User Defaults Not Working When Try… - Apple Developer
Hi,. When I try to save the information provided by the user on the Settings view and come back to the settings again...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Never mind, I see the problem. The syntax I used is deprecated as a top level keyword.
This issue is stale due to inactivity