Skip to content

docs: require screenshot/video for documentation PRs#6882

Open
tanupriyasingh1 wants to merge 2 commits into
pipe-cd:masterfrom
tanupriyasingh1:require-screenshot-docs
Open

docs: require screenshot/video for documentation PRs#6882
tanupriyasingh1 wants to merge 2 commits into
pipe-cd:masterfrom
tanupriyasingh1:require-screenshot-docs

Conversation

@tanupriyasingh1

Copy link
Copy Markdown

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?:

  • How are users affected by this change: Contributors will now see a new section in the PR template asking for screenshots/videos when submitting documentation or website changes.
  • Is this breaking change: No
  • How to migrate (if breaking change): N/A

Signed-off-by: tanupriyasingh1 <tanuwu101@gmail.com>
@tanupriyasingh1 tanupriyasingh1 requested a review from a team as a code owner May 30, 2026 20:39
@rahulshendre rahulshendre added area/docs kind/enhancement New feature or request and removed area/build labels Jun 12, 2026
Comment thread .github/PULL_REQUEST_TEMPLATE.md Outdated
Comment on lines +21 to +25
If AI tools were used to assist this PR:
- You must have personally reviewed, tested, and understood all changes before submitting
- Disclose AI usage in the PR description
- Do not list AI tools as co-authors in commits
- PRs that appear untested or unreviewed may be closed without review -->

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

should have AI disclosure in our PR template 👀
@Ayushmore1214, @mohammedfirdouss, @armistcxy what do you folks thing

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

IMO, these looks like rules and should be put in the guidance, not in the PR template

Reference: https://github.com/kubernetes/community/blob/main/contributors/guide/pull-requests.md#ai-guidance

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks for the suggestion @armistcxy, yes this is already being worked on in a another PR

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@tanupriyasingh1 plz take a look here whenever you have time!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

should have AI disclosure in our PR template 👀 @Ayushmore1214, @mohammedfirdouss, @armistcxy what do you folks thing

not in PR template but guidelines in a MD file for example.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@mohammedfirdouss yes this is already being wokred on here #6815 do take a look if you have some time thanks!

Comment thread .github/PULL_REQUEST_TEMPLATE.md Outdated

**Screenshots/Videos (for documentation or website changes)**:

<!-- If your PR modifies files under docs/ or any .md/.mdx files:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@tanupriyasingh1 one question: why is this comment required here ?

Comment thread .github/PULL_REQUEST_TEMPLATE.md Outdated
Comment on lines +21 to +25
If AI tools were used to assist this PR:
- You must have personally reviewed, tested, and understood all changes before submitting
- Disclose AI usage in the PR description
- Do not list AI tools as co-authors in commits
- PRs that appear untested or unreviewed may be closed without review -->

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks for the suggestion @armistcxy, yes this is already being worked on in a another PR

Comment thread .github/PULL_REQUEST_TEMPLATE.md Outdated
Comment on lines +21 to +25
If AI tools were used to assist this PR:
- You must have personally reviewed, tested, and understood all changes before submitting
- Disclose AI usage in the PR description
- Do not list AI tools as co-authors in commits
- PRs that appear untested or unreviewed may be closed without review -->

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@tanupriyasingh1 plz take a look here whenever you have time!

@armistcxy

Copy link
Copy Markdown
Contributor

@rahulshendre This is one of the reason why I advocate your idea of using Netlify. It supports preview document changes and we no longer need additional require for PR template

@tanupriyasingh1

Copy link
Copy Markdown
Author

Hey @Ayushmore1214! The comment block was meant to provide hidden guidance to contributors, but I agree it's not the right approach since it hides all the useful content beneath the heading. I'll replace it with a simple visible instruction line instead. Thanks for pointing that out!

@tanupriyasingh1

Copy link
Copy Markdown
Author

Removing the AI disclosure section from this PR since it's already being handled in #6815. Will also simplify the screenshots comment block into a clean visible instruction. Will push the updated commit shortly

@rahulshendre

Copy link
Copy Markdown
Contributor

@rahulshendre This is one of the reason why I advocate your idea of using Netlify. It supports preview document changes and we no longer need additional require for PR template

Agreed, Netlify preview deploys would make this unnecessary long-term. Until then, the screenshots section is a good interim measure.
@tanupriyasingh1 since the AI disclosure is already being covered, can you update this PR to just keep the screenshots part?

@tanupriyasingh1

Copy link
Copy Markdown
Author

hey @rahulshendre I've pushed the updated changes. PTAL whenever you have time

@Ayushmore1214 Ayushmore1214 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@rahulshendre rahulshendre left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM
Thanks @tanupriyasingh1 🙌

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

Labels

area/build kind/enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Require screenshot/video for documentation PRs to ensure local verification

5 participants