Commit 3affe504 authored by Cynthia "Arty" Ng's avatar Cynthia "Arty" Ng
Browse files

Add MultiLineLinks rule and fix errors

parent 3dac2eab
Loading
Loading
Loading
Loading
+14 −0
Original line number Diff line number Diff line
---
# Error: handbook.MultiLineLinks
#
# Checks that links are all on a single line.
#
# For a list of all options, see https://vale.sh/docs/topics/styles/
extends: existence
message: "Put the full link on one line, even if the link is very long."
link: https://docs.gitlab.com/ee/development/documentation/styleguide/index.html#links
level: error
scope: raw
raw:
  - '\[[^\[\]]*?\n[^\[\]]*?\]\([^\)]*?\)|'
  - '\[[^\[\]]*?\]\([^\)]*?\n[^\)]*\)'
+1 −2
Original line number Diff line number Diff line
@@ -10,8 +10,7 @@ Description: Migration report for moving the handbooks communication section
Please complete the following tasks:

- [x] Review the MR in handbook for the new content
  - MR Link: [https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/376](
https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/376)
  - MR Link: <https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/376>
- [x] Fix outstanding markdown lint errors
- [x] Merge MR for `handbook`
- [x] Review the MR in `www-gitlab-com` for the removal of the old content
+1 −3
Original line number Diff line number Diff line
@@ -10,9 +10,7 @@ Description: Migration report for moving the handbooks support section
Please complete the following tasks:

- [x] Review the MR in handbook for the new content
  - MR Link: [branch 'add-support-to-handbook' set up to track 'origin/add-support-to-handbook'.
https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/323](
https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/323)
  - MR Link: [branch 'add-support-to-handbook' set up to track 'origin/add-support-to-handbook'](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/323)
- [x] Fix outstanding markdown lint errors
- [x] Merge MR for `handbook`
- [x] Review the MR in `www-gitlab-com` for the removal of the old content
+1 −2
Original line number Diff line number Diff line
@@ -149,8 +149,7 @@ The process is comprised of five key stages:
        1. Complete term sheet ([template](https://docs.google.com/document/d/1_G2bXxhMe_qXrF8LdZcXwsCcIs1GJAS1-v42U2MV8a4/edit)) draft with proposed details (asset payment, retention bonuses, Deal Milestones, closing schedule, customer termination and closing conditions) filled in.
    1. Functional approvals: The Corporate Development, Product and Engineering Champions will present the business case for acquisition to the CPO, CTO and CRO. They will review to approve the items listed in the Champions' approval (complete: executive summary, business case, term sheet)
    1. CEO, CFO and CLO approvals: The Corporate Development, Product and Engineering Champions will present the business case for acquisition to the CEO, CFO and CLO. This meeting will also capture the **explicit approval** of the term sheet to start negotiations.
        1. Approval of term sheet to start negotiations will be tracked in a [term
        sheet approval issue](<https://gitlab.com/gitlab-com/corporate-development/issues/new?issuable_template=term_sheet_approval>). We don't include any financial and milestone information in the approval tracking issue for confidentiality reasons.
        1. Approval of term sheet to start negotiations will be tracked in a [term sheet approval issue](https://gitlab.com/gitlab-com/corporate-development/issues/new?issuable_template=term_sheet_approval). We don't include any financial and milestone information in the approval tracking issue for confidentiality reasons.
1. Term Sheet:
    1. Once the terms to start negotiations have been approved, the Corporate Development Deal Champion will reach out to the target company to share the offer and term sheet.
    1. Once an agreement on terms with the target has been reached, the term sheet (with any changes) will be brought forward for approval from: CLO, CFO, CEO (in that order). These approvals will be captured in the term sheet approval issue.
+1 −10
Original line number Diff line number Diff line
---

title: "How To Use Google Calendar Delegate"
---








## Introduction

The purpose of this handbook page is to describe how to utilize [Google
Calendar Delegation](https://support.google.com/a/users/answer/168126?hl=en#:~:text=When%20you%20set%20up%20mail,parts%20of%20your%20account%E2%80%8B.). Google Calendar delegation gives the ability to for a team member to access
The purpose of this handbook page is to describe how to utilize [Google Calendar Delegation](https://support.google.com/a/users/answer/168126?hl=en#:~:text=When%20you%20set%20up%20mail,parts%20of%20your%20account%E2%80%8B.). Google Calendar delegation gives the ability to for a team member to access
another team member's Google Calendar.

There are different [Levels of Permissions](https://support.google.com/a/users/answer/37082#Delegate_Calendar&zippy=%2Cunderstand-permission-settings-for-shared-calendars) that can be assigned to Google Calendar Delegation.
Loading