Skip to main content

GitHub Records (Moderators Only)

Open the GitHub Warning Book to create/update member logs.

Open Warning Book

All moderation actions must be recorded in the GitHub Warning Book to keep history consistent and searchable.

Why this matters

Clear records help us make fair decisions, see patterns, and coordinate as a team.

Step-by-step​

  1. Close the ticket properly (confirmation, acknowledgement, reason)
  2. Open the member's issue in the GitHub Warning Book, or create a new one if none exists
  3. Add/update the latest incident log using the template below
  4. Apply/update labels for active warnings
  5. If appropriate, add the member to the watchlist channel/thread for follow-up visibility

🔑Access

  • Open the GitHub Warning Book (linked in the mod-special channel).
  • Direct link: GitHub Warning Book
  • Make sure you are signed in with the correct account.

✅After Closing a Ticket

  • The @Moderator on call records the outcome in GitHub.
  • Include a brief summary of what happened.

🆕New Issue Naming

  • If the member has no prior record, create a new issue with:
  • Discord Tag + [Discord ID] in the title
  • Profile screenshot in the body
  • Example: FictionalUser [123456789012345678]

📝What to Log

  • Date/time of the incident
  • Which rule was broken
  • Punishment applied
  • Screenshot(s) of the ticket or evidence

🏷️Labels

  • Use labels to track number of active warnings.
  • Warnings are active for 1 week and stack during that period.

📈Update Levels

  • Move member to the appropriate warning/ban level per Server Guidelines.
  • Keep entries concise, factual, and neutral.

Logging Template​

Copy and paste this into the GitHub issue body, then replace the bracketed fields:

When: [YYYY-MM-DD HH:mm TZ]
Why: [Short reason / rule broken]
Result: [Warning issued / Ticket closed with reason / Timeout Xh / Ban vote opened]
Logged By: [Your Mod Name]

Evidence:
- [Link to ticket screenshot]
- [Second link if applicable]

Notes:
- [Optional notes]
Watchlist

If this member needs continued visibility, add a brief summary in the watchlist channel/thread after logging the incident. Keep it factual and short.

Visual Example​

Draft
FictionalUser [123456789012345678]
When: 2024-06-16
Why: Oversharing/Negativity in public channels.
Result: No acknowledgement from user, informal warning issued.
Logged By: Moderator 1
Profile
FictionalUser
Mutual Friends (0) • Mutual Servers (1)
Member Since • 16 May 2020
Note: Profile screenshot placed here to match GitHub entry.
Keep it accurate

Accurate record‑keeping is essential for consistency and fairness across cases.