Skip to content

Conversation

@JelteF
Copy link
Collaborator

When a commitfest is closed authors currently need to move their patches. This
is an attempt to "age out" patches without interest automatically. This has a
few downsides though. For patches that have activity going on, this is just
busywork for the author. And currently it's not even very clear that authors
are expected to do this (i.e. it's only shown in the dashboard).

So this PR tries to improve the situation in three ways:

  1. Automatically move "active" patches to the next commitfest
  2. Send email notifications to authors for patches that were not moved
    automatically
  3. Show a warning on the patch page

@JelteFJelteFforce-pushed the friendly-cf-close-handling branch from f19044a to d3f1fc7CompareJanuary 5, 2026 08:12
@JelteFJelteFforce-pushed the friendly-cf-close-handling branch from d3f1fc7 to e5f615bCompareJanuary 5, 2026 08:15
@JelteFJelteF merged commit 208d89b into mainJan 5, 2026
2 checks passed
@JelteFJelteF deleted the friendly-cf-close-handling branch January 5, 2026 08:18
JelteF added a commit that referenced this pull request Jan 23, 2026
When a commitfest is closed authors currently need to move their patches. This is an attempt to "age out" patches without interest automatically. This has a few downsides though. For patches that have activity going on, this is just busywork for the author. And currently it's not even very clear that authors are expected to do this (i.e. it's only shown in the dashboard). So this PR tries to improve the situation in three ways: 1. Automatically move "active" patches to the next commitfest 2. Send email notifications to authors for patches that were not moved automatically 3. Show a warning on the patch page
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@JelteF