Update @ahmed.hemdan team file to become maintainer for some sast analyzers
Why is this change being made?
This merge request updates my own team file to become a maintainer for some SAST analyzers to reflect the following merge requests:
- gitlab-org/security-products/analyzers/secrets!234 (closed)
- gitlab-org/security-products/analyzers/mobsf!85 (closed)
- gitlab-org/security-products/analyzers/kubesec!91 (closed)
- gitlab-org/security-products/analyzers/pmd-apex!112 (closed)
- gitlab-org/security-products/analyzers/phpcs-security-audit!90 (merged)
Please merge only when those are merged as well.
Author Checklist
-
Provided a concise title for this Merge Request (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, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - 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 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
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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.