Repository navigation
docs: mention getError() in signal forms skill - #71166
Merged
kirjs merged 1 commit intoOct 5, 2026
Merged
kirjs merged 1 commit into
kirjs merged 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
JeanMeche
approved these changes
Oct 3, 2026
Copy link
Copy Markdown
Contributor
|
This PR was merged into the repository. The changes were merged into the following branches: |
Sorry, something went wrong.
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The signal forms skill has no mention of getError().
Issue Number: #71164 (this PR is the skill portion of this issue's skill & docs change request)
What is the new behavior?
The signal forms skill has a couple mentions of getError().
Does this PR introduce a breaking change?
Other information