Skip to content

Conversation

@rshade
Copy link
Contributor

@rshade rshade commented Nov 13, 2025

Clarify review instructions for SDK files.

Clarify review instructions for SDK files.
@rshade rshade added the impact/no-changelog-required This issue doesn't require a CHANGELOG update label Nov 13, 2025
@rshade rshade requested a review from Copilot November 13, 2025 22:10
@github-actions
Copy link

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

Maintainer note: consult the runbook for dealing with any breaking changes.

@codecov
Copy link

codecov bot commented Nov 13, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 19.89%. Comparing base (ecd54ce) to head (3d7e255).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #604   +/-   ##
=======================================
  Coverage   19.89%   19.89%           
=======================================
  Files          48       48           
  Lines        5700     5700           
=======================================
  Hits         1134     1134           
  Misses       4399     4399           
  Partials      167      167           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a new instruction file to provide guidance on when and how to review SDK-related files, specifically in relation to schema.json changes and auto-generated SDK code.

  • New instruction file .github/sdk.instructions.md created with guidelines about SDK file review requirements
  • References the make build_sdks command for SDK regeneration
  • Clarifies that SDK files are auto-generated

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@@ -0,0 +1,2 @@
If schema.json has changed, verify that the SDK files in this folder have been regenerated by running `make build_sdks`.
Otherwise, the files in this folder are auto-generated and should not be reviewed.
Copy link

Copilot AI Nov 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The phrase "the files in this folder" is ambiguous since this instruction file is in .github/ but refers to files in the sdk/ folder. Consider making this more explicit: "Otherwise, the files in the sdk/ folder are auto-generated and should not be reviewed."

Suggested change
Otherwise, the files in this folder are auto-generated and should not be reviewed.
Otherwise, the files in the `sdk/` folder are auto-generated and should not be reviewed.

Copilot uses AI. Check for mistakes.
Copy link
Member

@iwahbe iwahbe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there some standard for .github/sdk.instructions.md? If so, can you link it?

It's not obvious why this is the best way to describe the sdk folder otherwise.

@rshade
Copy link
Contributor Author

rshade commented Nov 14, 2025

Is there some standard for .github/sdk.instructions.md? If so, can you link it?

It's not obvious why this is the best way to describe the sdk folder otherwise.

Not really, I wish we had one. We really just need copilot to ignore the whole thing unless the schema changes, but maybe people will just know that the unclean checkout means run make build_sdks, and we can just do #4 on here: https://docs.github.com/en/copilot/how-tos/configure-custom-instructions/add-repository-instructions#creating-path-specific-custom-instructions-2, what do you think

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

impact/no-changelog-required This issue doesn't require a CHANGELOG update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants