Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Audit trail for state and delegate changes

未關閉
#597 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
python
領域
backend, databases

研究方向

未指定檔案、測試或進入點。先找出套用狀態並委派變更的程式碼，接著決定應如何定義及查詢提議的稽核記錄。完成的定義是有一份達成共識的設計及實作，針對相關變更記錄修補程式 ID、使用者、先前值和新值。

由索引模型根據 Issue 內容生成。

描述

Greetings,

I hope I am not creating a duplicate here, but I would like to ask if there is a plan for implementing logs for field changes connected with the user performing that action.
Why do we need this? Patches can easily "disappear" from the system when an incorrect state change is performed, like when a patch is declared completed it will disappear from the list of items where an action is required. Nobody will regularly look through other states on the off chance of finding an incorrectly modified item. Now at some point, these errors will be uncovered when the submitter of a patch complains and at that point, we want to know how that error could have happened. Was it an error from a bot handling patches? Was it an unintended or malicious change by a maintainer?
It would be optimal if a database table is filled with the field changes, containing the ID of the patch, the name of the user, the previous field value, and the new field value. Then it would be easy to find the offending action.

What do you think about this?

Regards,
Sebastian

主要語言
Python
星號
317
分支
91
30 天內沒有已合併 PR

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

getpatchwork/patchwork 的其他 Issue

查看 getpatchwork/patchwork 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。