AlphaThis is a new service – your feedback will help us to improve it.

  1. Home
  2. Documentation
  3. Cloud Optimisation and Accountability
  4. Low GitHub Seats Response Procedure

Low GitHub Seats Response Procedure

Low GitHub Seats Response Procedure

Overview

This document outlines the steps to follow when an alarm is triggered in our Slack channel, indicating potential issues with dormant users or low GitHub seats.

Steps to Follow

Initiate Dormant Users Process:

On receiving an alarm in Slack, start the "Dormant Users" process as described in our runbook.

Retrigger GitHub Action:

After completing the Dormant Users process, retrigger the "check-for-low-github-seats" GitHub action to reassess the seat count.

If the GitHub action retriggers the alarm, indicating a continued issue with low GitHub seats, contact Head of Hosting.

Last reviewed: 1 July 2025Review status: ✗ Review overdueOwner: #operations-engineering-alertsSource: View source on GitHub

Was this page useful?