Skip to content

Comments

Add AI Contribution Policy to CONTRIBUTING.md#36651

Merged
lunny merged 19 commits intogo-gitea:mainfrom
silverwind:aipolicy
Feb 21, 2026
Merged

Add AI Contribution Policy to CONTRIBUTING.md#36651
lunny merged 19 commits intogo-gitea:mainfrom
silverwind:aipolicy

Conversation

@silverwind
Copy link
Member

@silverwind silverwind commented Feb 17, 2026

Based on my recent experience of both using AI tools and reviewing AI-generated pull requests. Partially based on https://typescript-eslint.io/contributing/ai-policy/.

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Feb 17, 2026
Signed-off-by: silverwind <me@silverwind.io>
@wxiaoguang
Copy link
Contributor

wxiaoguang commented Feb 17, 2026

By the way, I was thinking about splitting the CONTRIBUTING.md into different files.

There are too many contents mixed together in CONTRIBUTING.md, many of them are for maintainers only, not needed by contributors.

In my mind, some files:

  1. CONTRIBUTING.md: only contains the useful information for new contributors, and link to other files
  2. docs/guideline-frontend.md
  3. docs/guideline-backend.md
  4. docs/community-governance.md
  5. docs/release-management.md

Otherwise, the all-in-one file which has more than thousand of lines (wrapping....) is difficult to read, and the useful information can be easily ignored (for example: don't rebase+force-push)

@silverwind
Copy link
Member Author

Yeah, makes sense to split up that huge file.

Signed-off-by: silverwind <me@silverwind.io>
Copy link
Contributor

@TheFox0x7 TheFox0x7 left a comment

Choose a reason for hiding this comment

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

Overall seems like a good starting point. I'll hold on ACK for the other thread to be resolved.

Co-authored-by: TheFox0x7 <thefox0x7@gmail.com>
Signed-off-by: silverwind <me@silverwind.io>
@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Feb 20, 2026
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Feb 20, 2026
@lunny lunny added the reviewed/wait-merge This pull request is part of the merge queue. It will be merged soon. label Feb 20, 2026
@lunny lunny merged commit bb41bca into go-gitea:main Feb 21, 2026
26 checks passed
@GiteaBot GiteaBot added this to the 1.26.0 milestone Feb 21, 2026
@GiteaBot GiteaBot removed the reviewed/wait-merge This pull request is part of the merge queue. It will be merged soon. label Feb 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. modifies/docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants