Show the history of patch state changes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named. Start by locating where patch states are stored and changed, and review the dependency on issue #40. Done should include persisted state changes and a way to display the complete patch-state history, but the issue does not define the interface or tests.
Written by the indexing model from the issue text.
Description
There is interest to have the history of patch states, time to actually log an issue.
This depends on actually storing that information (same as https://github.com/dlespiau/patchwork/issues/40)
OpenEmbedded/Yocto would also like that: https://bugzilla.yoctoproject.org/show_bug.cgi?id=8704
- Dominant language
- Python
- Stars
- 22
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dlespiau/patchwork
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in dlespiau/patchwork
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100