Erran Carey Out of Office Coverage (June 27, 2023 - July 11, 2023)
Please reference this issue if you're unsure whom to contact or whether to wait for my return.
TL;DR — feel free to ping me in Slack or GitLab for items that need my attention when I return. Please use GitLab issues otherwise and tag the appropriate DRI as outlined below.
For the Neovim GitLab plugin (e.g. Neovim Code Suggestions):
- Refer to the following Neovim GitLab plugin meeting notes (internal document)
- Please reach out to
#f_neovim_plugin
(internal). - Please create issues under https://gitlab.com/gitlab-org/editor-extensions/gitlab.vim.
- Optional: Mention Kai (Product Manager) if labels/prioritization is required
/cc @phikai
. - Optional: Mention Ash (Engineer) and André (Engineering Manager) who are covering on the engineering side of things
/cc @ashmckenzie @andr3
.
For all Breach and Attack Simulation features:
- Please assign me via
/assign @erran
since I am the DRI. - Apply the IncubationBreach and Attack Simulation label via
/label ~"Incubation::Breach and Attack Simulation"
. - I last reviewed the status of all children under the epic gitlab-org&10579 was reviewed on
June 26, 2023 at 12:45am
.
For issues:
- Mention @erran or
/cc @erran
and I'll review this when back online.
For merge request reviews:
- For the GitLab Neovim plugin - Assign Ash who is covering for me:
/assign_reviewer @ashmckenzie
- DAST analyzer - Request a review through
#g_secure-dynamic-analysis
.- Perform a MR into my open MR as a base instead of committing changes directly to them for transparency.
- Browser-based analyzer - Request a review through
#g_secure-dynamic-analysis
.- Perform a MR into my open MR as a base instead of committing changes directly to them for transparency.
-
BAS.latest.gitlab-ci.yml
-/assign_reviewer @erran
or follow the regular GitLab review process and create a follow-up issue assigned to me if you're not able to wait for my return.
Edited by Erran Carey