Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Linkage of multiple cross-posted versions of patches

未关闭
#199 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
full-stack

调研方向

首先跟踪传入消息如何通过 Message-ID 进行匹配,以及 patch detail view 如何呈现项目和状态数据。定义跨项目链接,并验证 cross-posted patches 会显示链接以及适当的 Accepted、Changes Requested 或 Rejected 警告,而不会将它们合并为单个副本。

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

描述

enhancement

If a patch is cross-posted to two lists, it would be nice to indicate this in the UI so that maintainers on each side are aware that a patch is being seen on another list.

The easiest way to do this would probably be to add a ManyToMany and match incoming messages against any existing instances of that Message-ID in other projects. Then add appropriate links on the patch detail view, perhaps with a nice big warning if one of the other projects has marked it Accepted/Changes Requested/Rejected.

We may want to consider just keeping a single unified copy of a patch, but that would be a major behaviour change, and it's not clear to me exactly how we would make that work such as to keep a sensible maintainer workflow. But perhaps worth thinking about longer term.

(Requested by Stephen Rothwell after a conflict between linuxppc-dev and ppc-kvm showed up...)

主要语言
Python
星标
317
派生
91
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

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

getpatchwork/patchwork 的其他 Issue

查看 getpatchwork/patchwork 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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