fix: remove invalid disallowScopes sequence from workflow#43
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR fixes a GitHub Actions workflow YAML validation error in the Conventional Commits PR-title check by removing an invalid disallowScopes input value that was provided as a YAML sequence, even though the action expects a multiline string.
Changes:
- Removed
disallowScopes: []from the workflow to avoid YAML schema/type validation issues. - Kept existing Conventional Commits configuration (scopes not required; allowed types unchanged).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Removes the
disallowScopes: []line which caused a YAML validation error ("A sequence was not expected" at line 17). ThedisallowScopesinput expects a multiline string, not a YAML flow sequence. Since no scopes are being disallowed, removing the line is equivalent.