Your CI maintainer is leaving: transfer responsibility, not just workflow notifications

Use an exit inventory, not a promise to keep it green

Record named default-branch workflows, unresolved cause groups, proposed but unmerged changes, temporary quarantines and their removal conditions, account-held problems and the last inspected run evidence. Distinguish evidence already retained from an unverified state. A green last run does not prove somebody will investigate tomorrow's failure.

• Name the incoming investigation owner and the maintainer authorised to review and merge.
• Name the account holder for secrets, runners, permissions and billing.
• Record the supplier's end date and any handover deliverables agreed in the existing contract; do not invent an overlap period.

An alert recipient is not automatically the incoming owner

GitHub documents that editing the cron expression can change scheduled-workflow notifications, and reactivating a workflow can change them again. A notification preference alone does not establish an operational agreement. Have the authorised team confirm the intended alert route and acknowledge responsibility. Reading current settings and evidence is preferable to changing a schedule or running a production-effect workflow merely to test email.

• Do not hand over a departing person's password or private token.
• The account holder reviews supplier access and revokes it through the approved process after required handover.
• No accounts, settings, notifications or credentials were exercised for this guide.

Do not leave unresolved work inside a cancelled allowance

Give each open item an owner, status and next authorised action. A repair pull request awaiting merge is not an accepted default-branch fix. Keep exclusions visible: an expired secret or application defect is not resolved by reassigning the CI subscription. Terms for unfinished work and termination must be agreed with the actual supplier, not inferred from this worksheet.

• Retain safe run/job/revision evidence without exporting private logs or source.
• List any intentionally lost coverage separately from repaired checks.
• Confirm the date from which the incoming scope applies; never imply uninterrupted or emergency cover without written agreement.

Buy only the uncovered responsibility

An internal handover may be enough and has no new supplier fee, though staff effort remains real. The existing £295/month CI offer is relevant only for its one-repository named-workflow responsibility, up to four fixes and customer-held merges; it has no guaranteed response time. A single eligible residual configuration fault may fit £149 instead. If the gap is a wider existing-product backlog, the proposed US$10,000/month lane has one active item and at most four bounded planned items, not continuous CI monitoring or guaranteed completions. Do not bundle an exit checklist into a new package. Enquiry, secure access, scope and terms are separate; prices are untested and no monitoring or charge starts from reading this page.