Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

The 'Check' model should have an 'archived' field

Open
#70 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by locating the Check model and the Patch.combined_check_state function, then trace how the latest patch is selected for each user-context combination. Clarify how an archived field should represent state and how it should replace the current update approach; done means the archival state is stored on Check and the existing behavior is covered by the relevant tests.

Written by the indexing model from the issue text.

Description

enhancement

At the moment, the Patch.combined_check_state function is used to get the latest patch for each user-context combination. This allows us to continuously update a patch at we switch from state to state, e.g. pending -> failure. This is a bit of a hack though. We should instead store the archival state as part of the Check model.

Dominant language
Python
Stars
317
Forks
91
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getpatchwork/patchwork

All issues in getpatchwork/patchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.