💯 Towards 100 Checks for GitLab Detective
As of this writing we have 6 checks for GitLab Detective. Let's this use this issue to track and coordinate our efforts to getting to 100 checks.
See the README for more information about getting your local machine set up to develop checks. Read about creating a new check to get a quick overview of what's involved.
📋 Suggested Next Steps
Support Engineers reading this should consider...
- contributing ideas for checks in a new issue in this repo
- You don't have to write the check: open the issue so that we can work together to get the check written
- writing checks
- Set yourself as the Assignee for any issue where you are writing the check
- Ask in #spt_gitlab-detective if you have questions
Tough tickets and customer emergency retrospectives can be great sources of inspiration for check ideas.
1️⃣ Each One, Teach One
If you authored a check that has been successfully merged, help another Support Engineer get a check merged. Record who you helped and link to the MR introducing that check. Once you get a check merged, add your name here and help someone else get a check merged.
-
@bcarranza paired with @bnyaringita to get !40 (merged) merged -
@manuelgrabowski paired with @lalabi to get !56 (merged) merged -
@simonstreet paired with __ to get MR_REFERENCE merged -
@lalabi paired with __ to get MR_REFERENCE merged -
@bnyaringita paired with __ to get MR_REFERENCE merged
🤝 Contributor Success
As you successfully contribute checks and help others to do the same, keep an eye out for possible improvements to make it easier for any Support Engineer to get their first GitLab Detective check merged.
...but first
things we should consider before driving heavily towards 100 checks
Guidance on how to use the tool
Identify checks to be written systemically
Guidance on how to write checks
Why
Getting to 100 checks will help us with...