Prevent read after update

Author: robert-crandall

.github/skills/terraform-provider-pr-review/SKILL.md

@@ -84,5 +84,6 @@ If no issues are found, explicitly state `No blocking findings found` and list r
 - Prefer matching resource/data source tests when implementation behavior changes.
 - When schema or state semantics change, treat as high-risk unless compatibility is clearly preserved.
 - Breaking changes must follow semantic versioning: attribute removal/rename or new required fields warrant a major version bump.
+- Create/update functions in this provider intentionally do **not** call the read function afterward. This reduces API call volume against GitHub's rate limits and avoids stale reads from eventually-consistent endpoints (see [#2892](https://github.com/integrations/terraform-provider-github/issues/2892)). Do not flag this as an issue.
 - Example configurations under `examples/` should be self-contained, follow standard module structure, and not include `provider` blocks inside nested modules.
 - Sensitive attributes (tokens, secrets, private keys) must be marked `Sensitive: true` in the schema and must not appear in log output.

.github/skills/terraform-provider-pr-review/references/review-checklist.md

@@ -2,12 +2,15 @@
 
 Use this checklist when reviewing PRs in `terraform-provider-github`.
 
+ALWAYS acknowledge you are using this checklist when reviewing a PR!
+
 ## 1. Correctness and Behavior
 
 - Verify CRUD/read logic correctly maps GitHub API responses to Terraform schema/state.
 - Check for nil handling, default-value drift, and state flattening/expansion mismatches.
 - Confirm update paths do not accidentally force replacement or wipe optional fields.
 - Validate retry/backoff and error classification for API failures.
+- **Do not flag** create/update functions that return `nil` instead of calling the read function. This provider intentionally avoids read-after-write to minimize API calls against GitHub's rate limits and to avoid stale reads from eventually-consistent endpoints (see [#2892](https://github.com/integrations/terraform-provider-github/issues/2892)).
 
 ## 2. Schema and State Compatibility