docs: require screenshot/video for documentation PRs#6882
Open
tanupriyasingh1 wants to merge 2 commits into
Open
docs: require screenshot/video for documentation PRs#6882tanupriyasingh1 wants to merge 2 commits into
tanupriyasingh1 wants to merge 2 commits into
Conversation
Signed-off-by: tanupriyasingh1 <tanuwu101@gmail.com>
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
1 participant
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.
What this PR does:
Updates the PR template to add a screenshots/videos section for documentation and website changes, along with a note on AI-assisted contributions.
Why we need it:
Doc changes were being submitted without local verification, especially with the rise of AI tools among contributors. This ensures contributors have actually run and tested their changes locally before submitting, and gives reviewers a quick visual check.
Which issue(s) this PR fixes:
Fixes #6752
Does this PR introduce a user-facing change?: