doc(github_repository_webhook): Update GitHub repository webhook doc

[ViacheslavKudinov]

Resolves #3285

---

Before the change?

• it were used different names of the repo and webhook ID in the documentation and examples

After the change?

• for clarity in all the places of doc are used the same repo name and webhook ID

Pull request checklist

• Schema migrations have been created if needed (example)
• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes
• No

---

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[deiga]

Your commit history in this PR seems off :/

Instead of needing to explain foo-org and foo what if we change them to example-owner and example-repo?

[ViacheslavKudinov]

Your commit history in this PR seems off :/

Instead of needing to explain foo-org and foo what if we change them to example-owner and example-repo?

updated, hope its better

[ViacheslavKudinov]

Updated based on new way to generate doc
Nope, my bad. Did it in wrong folder 🫣

[deiga]

Files inside docs/ folder are generated files. You'll need to update the templates, examples and imports if you want to update this

[ViacheslavKudinov]

@deiga Could someone update Contributing to make it clear how we manage doc ?

[ViacheslavKudinov]

Files inside docs/ folder are generated files. You'll need to update the templates, examples and imports if you want to update this

Yep, will do, thanks.
Lost a little bit

PS But previous comment to update Contributing file still could help

[ViacheslavKudinov]

need to update similarly as #3414

[Copilot]

Pull request overview

These provider review instructions are being used. This PR updates the github_repository_webhook documentation and examples to consistently use the same repository name/webhook ID and to correct the import syntax (per #3285).

Changes:

• Switch the repository webhook docs template to the standard tfplugindocs pattern (examples via .ExampleFiles, schema via .SchemaMarkdown, and structured Import sections).
• Update provider schema descriptions to improve generated docs (including adding an etag description and linking to relevant API docs for secret).
• Add/adjust example and import snippets to use consistent names and the correct <repo>/<webhook_id> import format.

Reviewed changes

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

Show a summary per file

File	Description
templates/resources/repository_webhook.md.tmpl	Converts the doc template to the standard schema/examples/import rendering pattern and updates import wording.
github/schema_webhook_configuration.go	Enhances the secret attribute description with an API doc link for generated documentation.
github/resource_github_repository_webhook.go	Adds resource-level description, improves events description, adds etag description (but still has an incorrect url description).
examples/resources/github_repository_webhook/resource-1.tf	Renames example resources/values for consistency (example-repo, example_webhook).
examples/resources/github_repository_webhook/import.sh	Adds corrected CLI import example using example-repo/123456789.
examples/resources/github_repository_webhook/import-by-string-id.tf	Adds Terraform import block example using example-repo/123456789.
docs/resources/repository_webhook.md	Regenerated/updated docs reflecting the new template and corrected import examples.

[ViacheslavKudinov]

@deiga how should we react on Copilot reviews ?

[deiga]

@ViacheslavKudinov You review the comments and decide if they make sense. If you don't know, ask from other maintainers