nginx / nginx/documentation

[Bug]: Need more info in PR requests -- due to AI-generated submissions

Open
#2,014 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
94
Forks
174
Avg merge
1d 10h
Merged PRs (30d)
66

Description

Describe the problem you have identified

I'm not opposed to AI generated PRs, in most cases.

  • Exception: I want to preserve "Good first issues" for humans
  • Question: do we want to preserve "Good first issues" for people who are just starting their journey with Git? (How do we define that?)

GPT suggests we add more questions to PR templates, such as:


Did you use AI assistance?
[ ] No
[ ] Yes

If yes:
- Which tool?
- What was generated?
- Did you verify accuracy?
- Did you review for licensing concerns?

Then add:

Required human review
Vale and markdown lint checks
Link checking
Documentation tests
Security review for code samples
Which product or products does this problem relate to?

Other

If necessary, explain any additional steps to reproduce the problem.

No response

What is the expected or desired behaviour?

No response

Is this problem specific to a particular platform or software version?

No response

Any additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository's PR templates and the proposed Vale, markdown lint, link checking, documentation tests, and security review requirements. Confirm the project's policy on AI-assisted submissions and define the accepted questions and checks; the issue currently leaves the desired behavior and completion criteria open.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.