Repository navigation
Conversation
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.
Google Flow changes often enough that bug reports need a few specific details to be reproducible. This adds an issue form for compatibility regressions.
It collects the FlowKit commit, affected generation mode, sanitized request and error details, and whether the same action works in the Flow UI. Reporters can also include their browser/extension versions and minimal reproduction steps.
The form explicitly warns against posting cookies, Google auth or reCAPTCHA tokens, passwords, and private media URLs.
Only one YAML file is added. No runtime code, workflows, or funding settings change. The form will appear wherever the repository allows new issues.
Adapted from the compatibility report form in my FlowKit fork.