Document and enforce pull request review guidelines

未关闭 适合新手
#1,868 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@dashorst 已经在做这个了。

开始于 2026年11月8日。

  • #1869 来自 @dashorst —— 未关闭

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
76/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
java

调研方向

从 repository 根目录的 AGENTS.md 开始,了解现有贡献指南的组织方式。在根目录起草一份 REVIEW.md,涵盖 issue 中列出的七个审查领域,并在 AGENTS.md 中引用它。当这两个文件都为拟议的检查提供一致且实用的审查清单时,工作即告完成。

由索引模型根据 Issue 内容生成。

描述

Write down what a review of a Wicket pull request checks, so human and agent reviewers apply the same checks to every change, and make the checklist part of the workflow.

AGENTS.md describes how to write a change: format, commits, build, API compatibility, Javadoc, comments, security. Nothing describes what to check when reviewing one. The checks this issue should cover:

  • License compliance: ASF headers, the licenses of new dependencies under the ASF third-party policy, and LICENSE, LICENSE-binary, NOTICE and licenses/ for third-party code or assets copied into the tree.
  • OSGi and JPMS: the bundle manifest and module-info.java stay consistent with the pom when packages or dependencies change.
  • Performance: a change to a hot path keeps its complexity and memory footprint, or shows with a benchmark that the cost is worth it. During the dependency cleanup for #1862, a first draft replaced LinkedMap in MarkupContainer and made single child removal O(n).
  • Accessibility: markup, components and JavaScript that render UI keep meeting WCAG.
  • Documentation: changes users notice update the migration guide, user guide or Javadoc in the same pull request.
  • Serialization: changes to the serialized form of components and models, which affect stored pages and session size.
  • Tests: new test classes end in Test, or Surefire never runs them.

Proposal: a REVIEW.md in the repository root with these checks, referenced from AGENTS.md so agents writing a change check it against the same list.

主要语言
Java
星标
799
派生
420
平均合并
18 小时 37 分钟
30 天内合并 PR
140

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/wicket 的其他 Issue

查看 apache/wicket 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。