Skip to content

Draft: Adding troubleshooting_cheat_sheet.md

Keven Hughes requested to merge kevenhughes-adding-lr-troubleshooting-notes into master

Why is this change being made?

There's a lot of useful knowledge we've accrued over our time in Licensing and Renewals support that makes things easier, some of which doesn't easily fit elsewhere in the workflows sections, or maybe doesn't deserve a full handbook page such as quick-fixes or code blocks.

I like the idea of the GitLab Rails Console Cheat Sheet which originated as place for documenting useful infos, oneliners, how-tos, etc by support team for support team, so modeling that idea here as a place to start documenting my own knowledge and that of others.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this change to the correct DRI(s)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports