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 摘要。