GitHub Saved Replies
GitHub saved replies for common scenarios. These are team-approved responses - using them is expected and encouraged.
Saved replies are a team tool that lets us respond quickly, consistently, and professionally, without spending mental energy rewriting the same message again and again. By standardizing our responses to common situations, we free up focus for meaningful feedback and ensure consistent expectations and reduce friction for both contributors and reviewers.
Using these replies is encouraged - they give everyone permission to politely uphold our standards, set expectations, and enforce process, even in difficult or high-traffic moments.
To set up saved replies go to GitHub > Settings > Saved replies, and add all of the replies below.
Open an issue first (behavior/refactor -> close)
Thanks for the contribution! We ask that behavioral changes and refactors have a linked issue so we can discuss the approach before a PR is opened. Could you open an issue describing the problem you're solving and your proposed approach? Closing this for now - happy to revisit once there's an issue to reference.
Please also have a look at our CONTRIBUTING.md for more PR guidelines.
Let's discuss the approach first (idea -> close)
This is an interesting idea! We'd like to align on the approach before reviewing code - could you open an issue describing the problem and your proposed solution? That way we can agree on direction first. Closing this PR for now.
Please also have a look at our CONTRIBUTING.md for more PR guidelines.
Not ready for review (request changes / mark as draft)
Thanks for the contribution! This PR needs some updates before we can review:
- CI checks are passing
- PR description explains what and why
- Linked issue exists
- Tests are included
We marked it as draft for now. Please update and we'll take another look.
Please also have a look at our CONTRIBUTING.md for more PR guidelines.
Issue/Close: Inactivity
Closing this issue due to inactivity. If this is still relevant for you, please feel free to reopen or create a new issue with up-to-date information and we'll be happy to take another look.
Thank you for taking the time to report this!
Issue/Close: No response
We haven't heard back on this, so we're closing it for now. If you're able to provide the requested information, please feel free to comment and we'll reopen and take another look.
Thank you for taking the time to report this!
Issue/Close: Can't reproduce
We weren't able to reproduce this on our end. If you're still experiencing this issue and can share a minimal reproduction or additional details on how to trigger it, please feel free to comment and we'll reopen.
Thank you for taking the time to report this!
Issue/Close: Outdated / Superseded
Closing this as it has been superseded by newer SDK or platform versions, or by other issues that cover this topic. If you believe this is still relevant with a current SDK version, please feel free to comment with updated information and we'll reopen.
Thank you for taking the time to report this!
Issue/Close: Duplicate
This appears to be a duplicate of #ISSUE_NUMBER, so we're closing this to keep the discussion in one place. Please follow that issue for updates and feel free to add any additional context there.
Thank you for taking the time to report this!
Issue/Close: Working as intended
After looking into this, we believe the current behavior is working as intended. EXPLAIN_REASON_HERE
If you have a use case that isn't covered or think we've misunderstood the issue, please feel free to comment and we can revisit.
Thank you for taking the time to report this!
Issue/Close: Wrong repo
It looks like this issue belongs in a different repository. Could you please open it in REPO_LINK instead? That team will be better equipped to help.
Closing this for now. Thank you for taking the time to report this!
Issue/Acknowledge: Added to triage queue
Thanks for reporting. We've seen your request and added it to our triage queue.
We'll review it shortly and follow up if we need more information or once next steps are clearer.
Issue/Acknowledge: Reproduction info needed
Thanks for raising this. We're reviewing it as part of triage.
To move forward, could you share:
- SDK version
- Runtime / framework version
- A minimal reproduction (if available)?
Issue/Acknowledge: Valid low-prio feature request
Thanks for the report, we appreciate you taking the time to write this up!
We've looked into this and while we do think it's a valid issue, it's currently not something we're able to prioritize. We have other work on our roadmap that we consider more impactful to address first.
If this is important to you, we'd genuinely welcome a contribution. Feel free to open a PR and we'd be happy to review and guide you through the process. Please have a look at our contributing guidelines, and don't hesitate to ask questions here first.
We'll leave this open in case someone wants to pick it up!
Issue/Request: More information needed
Thanks for reporting this! To help us investigate, could you provide a few more details?
- SDK version: (e.g. 1.2.3)
- Platform/OS version: (e.g. iOS 17, Android 14, Node 20)
- Steps to reproduce: What were you doing when this occurred?
- Expected behavior: What did you expect to happen?
- Actual behavior: What happened instead?
- Logs or stack traces: If available
This will help us narrow things down. Thank you!
Issue/Request: Minimal reproduction needed
Thanks for reporting this! We'd love to look into it further, but we need a minimal reproduction to investigate effectively. Could you provide a small, self-contained project or code snippet that demonstrates the issue?
A good minimal reproduction:
- Uses the latest SDK version
- Contains only the code necessary to trigger the issue
- Includes steps to run and observe the behavior
This helps us rule out project-specific factors and get to the root cause faster. Thank you!
Issue/Redirect: Support channel
Thanks for reaching out! This looks like a usage or configuration question rather than a bug report or feature request. For the fastest help, we'd recommend reaching out through one of our support channels:
Our support team and community are well-equipped to help with setup and usage questions. If it turns out there is a bug, please feel free to open a new issue with reproduction steps and we'll investigate.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").