cloudflare / cloudflare/cfssl_trust
Transfer Scheduled Release workflow notifications from maxnystrom to a current maintainer
- Dominant language
- Go
- Stars
- 320
- Forks
- 77
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 2
Description
## Request
Please transfer notifications for the **Scheduled Release** workflow (`.github/workflows/scheduled-release.yml`) from my account, `maxnystrom`, to a current maintainer. I would like to stop receiving these notifications while keeping my other GitHub Actions notifications enabled.
## Why this is happening
I changed the workflow's cron schedule in [commit e31b55c](https://github.com/cloudflare/cfssl_trust/commit/e31b55c3965eb5db3c85c570f0c706d2230c08e8) on March 8, 2023. GitHub associates scheduled-workflow notifications with the user who last changed the cron schedule, unless another user subsequently disables and re-enables the workflow.
For example, [Scheduled Release run #286](https://github.com/cloudflare/cfssl_trust/actions/runs/34009015123) ran automatically on September 6, 2026, but lists `maxnystrom` as both its actor and triggering actor. It failed at the **Create pull request** step and I received a notification.
## Proposed fix
A current maintainer with the necessary permissions should, using **their own GitHub account**:
1. Open **Actions → Scheduled Release** in this repository.
2. Disable the workflow, then promptly re-enable it so scheduled releases continue.
GitHub documents that notifications for a scheduled workflow that is disabled and re-enabled go to the user who re-enabled it, rather than the user who last modified its cron syntax. This transfers notifications without requiring a schedule change.
Alternatively, a current maintainer can update the cron schedule; subsequent notifications will go to that user. A schedule change is not necessary if the disable/re-enable approach is used.
Reference: [GitHub — Notifications for workflow runs](https://docs.github.com/en/actions/concepts/workflows-and-actions/notifications-for-workflow-runs).
Please confirm once the notification handoff is complete. This request concerns notification routing; the pull-request creation failure may need separate investigation.
Contributor guide
Research direction
Review .github/workflows/scheduled-release.yml and the repository's Actions → Scheduled Release page. A current maintainer should perform the notification handoff with their own account while keeping scheduled releases enabled, then confirm that notifications no longer route to maxnystrom.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100