Skip to content
Snippets Groups Projects
Commit b24d4279 authored by Katrin Leinweber's avatar Katrin Leinweber Committed by Jason Colyer
Browse files

Replace mentions of outdated support email

parent 0e2c8026
1 merge request!83660Replace mentions of outdated support email
Showing
with 21 additions and 25 deletions
......@@ -76,7 +76,7 @@ If you have any further questions that aren't answered here, please follow the b
 
**Prospective Customers**: Please [fill out a request](https://about.gitlab.com/sales/) and a representative will reach out to you.
 
**Current Customers**: Please contact your [Account Owner](/handbook/sales/#initial-account-owner---based-on-segment) at GitLab. If you don't know who that is, please reach out to [support@gitlab.com](mailto:support@gitlab.com) and ask to be connected to your Account Owner.
**Current Customers**: Please contact your [Account Owner](/handbook/sales/#initial-account-owner---based-on-segment) at GitLab. If you don't know who that is, please [reach out to sales](https://about.gitlab.com/sales/) and ask to be connected to your Account Owner.
 
**GitLab Team Members**: Contact the Risk and Field Security team using the **Customer Assurance** workflow in the slack [#sec-fieldsecurity](https://gitlab.slack.com/archives/CV5A53V70) channel.
 
......
......@@ -28,7 +28,7 @@ The Customer Assurance Activities Procedure is applicable to Security due dillig
| | Provide information and documentation back to Customer or Prospect |
| **Solutions Architect** | Complete the First Pass, as applicable |
| **Current Customers** | Utilize Customer Self-Service tools noted below |
| |Contact your [Account Owner](/handbook/sales/#initial-account-owner---based-on-segment) at GitLab. If you don't know who that is, please reach out to [support@gitlab.com](mailto:support@gitlab.com) and ask to be connected to your Account Owner. |
| |Contact your [Account Owner](/handbook/sales/#initial-account-owner---based-on-segment) at GitLab. If you don't know who that is, please [reach out to sales](https://about.gitlab.com/sales/) and ask to be connected to your Account Owner. |
| **Prospective Customers** | [Fill out a request](https://about.gitlab.com/sales/) and a representative will reach out to you. |
 
## Customer Assurance Activities Workflow
......
......@@ -895,7 +895,7 @@ Customers can make payment through credit card, cheque and bank transfer. Paymen
 
- In the customer’s account page in Zuora, check the box [“Support Hold”](https://docs.google.com/document/d/1ahjMhYc9mZ5p_1w7aIu20oms4WJ1PCGEoGcQmr0SIIo/edit) under the Finance information section.
 
- Send an email to support@gitlab.com with the customer information - Account name, Account number, Invoice number, Due date, Days overdue, Balance, Entity, Support hold status, Comments stating when the reminder mails were sent.
- Contact us via [support.gitlab.com](https://support.gitlab.com/) with the customer information - Account name, Account number, Invoice number, Due date, Days overdue, Balance, Entity, Support hold status, Comments stating when the reminder mails were sent.
 
- **Credit hold for overdue payments**
 
......@@ -1151,6 +1151,3 @@ In case the system does not automatically provision the purchase/upgrade, or due
* Step 5: Click on “[save changes](https://docs.google.com/document/d/1qKa9m4FUe_TnfgqZCahPEPE9VkQKCERIP6pa0e1q0kA/edit)” to complete the change.
 
***Controls being implemented: QTC.C.50, QTC.C.51 & QTC.C.52***
......@@ -245,7 +245,7 @@ SMB Account Executives "SMB AEs" act as Account Executives and the face of GitLa
 
### Inbound Queue Management
 
**Zendesk:** Managing incoming requests received through support.gitlab.com, support@gitlab.com and renewals@gitlab.com
**Zendesk:** Managing incoming requests received through [support.gitlab.com](https://support.gitlab.com/) and [renewals@gitlab.com](mailto:renewals@gitlab.com)
 
**The goal and focus** of working Zendesk tickets for the SMB team is to help with **upselling** and **renewals**
 
......
......@@ -5,4 +5,4 @@ canonical_path: "/blog/2013/09/13/gitlab-in-the-changelog/"
categories: company
author: GitLab
---
The Changelog podcast interviewed our co-founder Sytse Sijbrandij yesterday. We want to thanks Andrew and Adam of the Changelog for chance to come on the show. In [the podcast](http://thechangelog.com/103/) we discuss the history of GitLab, the introduction of the Enterprise Edition, the awesome GitLab community and upcoming changes for GitLab 6.1. Media inquiries are always welcome at support@gitlab.com.
\ No newline at end of file
The Changelog podcast interviewed our co-founder Sytse Sijbrandij yesterday. We want to thanks Andrew and Adam of the Changelog for chance to come on the show. In [the podcast](http://thechangelog.com/103/) we discuss the history of GitLab, the introduction of the Enterprise Edition, the awesome GitLab community and upcoming changes for GitLab 6.1. Media [inquiries are always welcome](https://about.gitlab.com/press/#get-in-touch).
......@@ -15,4 +15,4 @@ GitLab is not affected by this vulnerability.
CVE-2014-3483 affects applications which use PostgreSQL [bitstring](http://www.postgresql.org/docs/9.2/static/datatype-bit.html) or [range](http://www.postgresql.org/docs/9.2/static/rangetypes.html) types in their database schema.
GitLab uses neither of these types in its database schema.
 
Please contact us at support@gitlab.com if you have any questions about this issue.
Please contact us at [support.gitlab.com](https://support.gitlab.com/)if you have any questions about this issue.
......@@ -18,4 +18,4 @@ GitLab 7.2 (to be released) does use `create_with` in two locations, but neither
 
We would like to thank Robert Schilling and Jeroen van Baarsen of the [GitLab core team](/community/core-team/) for their assistance in investigating this issue.
 
Please contact us at support@gitlab.com if you have any questions about this issue.
Please contact us at [support.gitlab.com](https://support.gitlab.com/)if you have any questions about this issue.
......@@ -19,4 +19,4 @@ Here you can simply set a regular expression that requires your rule in a commit
 
In addition, you can prevent users from deleting tags through pushes.
 
We're very excited about Git Hooks and are looking to add more. If you are a customer of GitLab and require a Git Hook, [tell us](mailto:support@gitlab.com) and we can implement it for free.
We're very excited about Git Hooks and are looking to add more. If you are a customer of GitLab and require a Git Hook, [tell us](https://support.gitlab.com/) and we can implement it for free.
......@@ -17,4 +17,4 @@ GitLab is not affected by this vulnerability.
CVE-2014-7818 affects Rails applications which have the `config.serve_static_assets = true` setting.
GitLab is shipped with `config.serve_static_assets` set to `false` in `config/environments/production.rb` because it lets NGINX (or Apache) serve static files.
 
Please contact us at support@gitlab.com if you have any questions about this issue.
Please contact us at [support.gitlab.com](https://support.gitlab.com/)if you have any questions about this issue.
......@@ -28,7 +28,7 @@ The GitLab B.V. team always treats them as top priority.
We give feedback within 1-2 days of notice.
Depending on the severity of the vulnerability, we will either patch GitLab, or fix the issue in the next minor release.
 
If you find a security bug in GitLab, please make sure to use [responsible disclosure](/security/disclosure/), and reach out to the GitLab B.V. team at support@gitlab.com.
If you find a security bug in GitLab, please make sure to use [responsible disclosure](/security/disclosure/), and reach out to the GitLab team via [support.gitlab.com](https://support.gitlab.com/).
 
## Regression bugs
 
......
......@@ -29,7 +29,7 @@ versions of Git (v1.8.5.6, v1.9.5, v2.0.5, v2.1.4, and v2.2.1).
- These major Git libraries, [libgit2](https://github.com/libgit2/libgit2/) and [JGit](https://eclipse.org/jgit/),
have released maintenance versions with the fix as well.
 
Please contact us at support@gitlab.com if you have any questions about this issue.
Please contact us at [support.gitlab.com](https://support.gitlab.com/)if you have any questions about this issue.
 
## About GitLab
 
......@@ -38,4 +38,3 @@ own server or by signing up to our free, unlimited GitLab instance [GitLab.com](
 
Check out [GitLab Enterprise Edition](/features/#enterprise) for deep LDAP integration, git hooks,
Jenkins integration and many more powerful enterprise features.
......@@ -85,7 +85,7 @@ You need to set up a project on GitLab.com and add it to ci.gitlab.com before yo
 
To claim it please fill out [this form](https://docs.google.com/a/gitlab.com/forms/d/1YXTRwDz2C8o4DqNrFCT78UQf_iHnN1Ekrt4p8yv6fd4/viewform) with your name, email or handle and project url.
Once submitted, the GitLab team will email you your unique promo code.
If you have any questions about this promotion, please contact the GitLab support team at support@gitlab.com.
If you have any questions about this promotion, please contact the GitLab support team via [support.gitlab.com](https://support.gitlab.com/).
 
## On your server
 
......
......@@ -98,4 +98,4 @@ and features.
 
 
[disclosure]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#security-vulnerability-disclosure
[release]: /2016/03/22/gitlab-8-6-released/
\ No newline at end of file
[release]: /2016/03/22/gitlab-8-6-released/
......@@ -25,7 +25,7 @@ We have performed an initial investigation and found no evidence to suggest that
 
In keeping with our [company value of transparency](/handbook/values/#transparency) we also believe in communicating about such incidents clearly and promptly. We apologize for the impact this issue may have caused to our users. GitLab takes securing your information and your data extremely seriously. We have significantly grown the size of our internal security team in the last six months, with further plans to grow in 2019 and beyond. We will learn from this incident as we continue to improve upon our security posture even further.
 
If you have any questions, please contact support@gitlab.com.
If you have any questions, please contact us via [support.gitlab.com](https://support.gitlab.com/).
 
*Updated on March 28, 2019*
We are modifying our previous recommendation for users who have automation in place that may have been impacted by the runner registration token reset. The paragraph should read as the following:
......
......@@ -70,9 +70,9 @@ Should you require additional assistance recovering your repository contents, pl
- Bitbucket:
Please contact Bitbucket Support by filing a request at [support.atlassian.com/contact/#/](https://support.atlassian.com/contact/#/) and selecting “Bitbucket Cloud” when prompted for a product.
- GitHub:
Please contact GitHub Support at [github.com/contact](https://github.com/contact) or support@github.com.
Please contact GitHub Support at [github.com/contact](https://github.com/contact).
- GitLab:
Please contact GitLab Support at [about.gitlab.com/support/#contact-support](/support/#contact-support) or support@gitlab.com.
Please contact GitLab Support via [support.gitlab.com](https://support.gitlab.com/).
 
## What the software development platform community is doing to protect users
 
......
......@@ -18,4 +18,4 @@ Gitlab.com now runs on Gitlab 3.1. Among other things it offers:
- Improved File Browsing
- Performance of commits is significantly improved
 
Hope you enjoy it. Feedback is welcome on support@gitlab.com as always.
\ No newline at end of file
Hope you enjoy it. Feedback is welcome via [support.gitlab.com](https://support.gitlab.com/) as always.
......@@ -9,4 +9,4 @@ categories: releases
Today we have published a [security advisory and updates](/blog/2013/12/05/gitlab-ce-6-dot-3-dot-1-released/) for GitLab Community Edition 6.3 and GitLab Enterprise Edition 6.3 in response to a recent security patch for Ruby on Rails.
For more information please see our blog post on [GitLab.org](/blog/2013/12/05/gitlab-ce-6-dot-3-dot-1-released/).
 
Subscribers of GitLab.com can contact us at support@gitlab.com for more information.
Subscribers of GitLab.com can contact us at [support.gitlab.com](https://support.gitlab.com/)for more information.
......@@ -10,4 +10,4 @@ We have just released GitLab Enterprise Edition 6.6.2, which fixes an HTML injec
We advise all users who install GitLab Enterprise Edition 6.6 to [update to 6.6.2-ee immediately](https://gitlab.com/subscribers/gitlab-ee/blob/master/doc/update/upgrader.md).
 
GitLab Enterprise Edition versions 6.5 and lower are not affected by this HTML injection vulnerability.
Please contact us at support@gitlab.com if you have any questions.
Please contact us at [support.gitlab.com](https://support.gitlab.com/)if you have any questions.
......@@ -14,4 +14,4 @@ We recommend everyone to upgrade their GitLab installation to the latest version
We have also released new packages for Ubuntu, Enterprise Linux and Debian. GitLab Enterprise Edition packages can be found in the subscribers repository. GitLab Community Edition packages are found [here](https://www.gitlab.com/downloads).
 
 
Please contact us at support@gitlab.com if you have any questions.
Please contact us at [support.gitlab.com](https://support.gitlab.com/)if you have any questions.
......@@ -11,4 +11,4 @@ We have released GitLab CI 5.0.1 because of the recent Rails security vulnerabil
 
We recommend everyone to upgrade their GitLab CI installation to the latest version using our [upgrade guide](http://doc.gitlab.com/ci/update/patch_versions.html).
 
Please contact us at support@gitlab.com if you have any questions.
Please contact us at [support.gitlab.com](https://support.gitlab.com/)if you have any questions.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment