Skip to content

Frontend merge request coach to Alexander Turinske

Alexander Turinske requested to merge update-alexander-merge-request-coach into master

Why is this change being made?

I would like to become a merge request coach

  • Why you want to become a Merge Request Coach? I want to become a Merge Request Coach because I enjoy mentoring to help people grow. I currently mentor new graduates from the coding accelerator I went to and I have already spent time helping community contributors in my part of the code base
  • How much time you are planning to spend on it? A couple of hours a week
  • Which duties you are focusing on (e.g. triage, finish stale MRs)? Mentorship, but that is only because that is all I have done so far. I am interested in expanding my skillset

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
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • 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 relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.
Edited by Alexander Turinske

Merge request reports