GitLab Onboarding

Other pages


On this page


Onboarding How To

Welcome to GitLab

Congratulations on completing the interview process, and starting your first day at GitLab. We are so excited that you are here! This page is designed to help you navigate the onboarding process from reading the handbook, to completing the onboarding issue. Regardless of your role, we all use GitLab, and if you come from a non-technical background, this might be new to you! At times the onboarding issue might feel overwhelming, but if you have any additional questions along the way, please feel free to ask People Ops, your buddy, or anyone else at GitLab in the #questions channel on Slack.

Your First Day

Throughout your first few weeks at GitLab it is important to focus on the onboarding issue. The onboarding issue is specific to you, for an idea what is in there please see the template. This guide will help you understand what is in the onboarding issue, and why we are asking you to complete the items on the issue.

Getting Started

Working Remotely

  1. The first month at a remote company can be hard. Take a look at 3 Things I Learned in My First Month at GitLab for some insight from a GitLabber.

The Onboarding Issue

In the onboarding issue, we ask you to complete a variety of tasks. Here are some tips on items like gmail, zoom, calendly, etc. The onboarding issue can be seen at the bottom of this page.

1Password

We recommend that you set up your 1Password account early in the onboarding process since you will need it to hold all of the new passwords that you will create. This is an awesome tool, that GitLab uses to store all passwords for each department. You will also have your personal vault where you can store all the passwords that you are creating for GitLab. In keeping with our security best practices. We ask that you do set up this 1Password account with your GitLab email, even though you might have one already.

2FA

GitLab asks you to enable 2FA (2-Step Verification, also known as two-factor authentication), because it adds an extra layer of security to your account. You sign in with something you know (your password) and something you have (a code sent to your phone). If you have problem with 2FA just let people ops know! We can disable it for you to then set it up again. If the problem persists, then we can direct you to one of our super admins.

BambooHR and TriNet

BambooHR is our HRIS (Human Resource Information System) for all team members. We have self-service enabled so that at any time you can access your account to see your employment information and documentation. As part of onboarding, please make sure to update everything that is applicable to you on the Personal tab, your ethnicity (which is located on the Jobs tab), and emergency contact information. We also ask that you provide People Ops with a Photo ID which is used for Employment Verification Purposes. You can send this documentation in any way you feel most comfortable. Some common ways in the past have been emailing People Ops, sending as a direct message to our People Ops Specialist in Slack, or scheduling a call with our People Ops Specialist to view the documentation.

The information from BambooHR is used to feed other systems, so it is important that it is filled out before you start. If you are a GitLab Inc. employee, you will receive login information from TriNet, our payroll and benefits provider, within 24 hours of your start date.

GitLab.com vs Dev.GitLab.org

The dev server is only viewable to team members, and is used by the Development team (amongst others). Per the GitLab workflow point 9, everything that can be public should be out in the open. GitLab.com is viewable to anyone with an account. We ask you to set up your GitLab.com account with your GitLab email for additional security.

Calendly

Calendly is a calendar tool that allows individuals to select open meeting slots in order to speak with others at the company. (Great for also setting up coffee breaks!) All team members add Calendly to their Slack profile as a part of onboarding, so if you ever need or want to speak with another team member, you can schedule the meeting yourself. When you are setting up Calendly, there is no specific GitLab account. With the free version you will only be allowed one meeting time, but if you need to upgrade to a Pro account, you can do so and expense it per spending company money.

Egencia

You will receive an email to set up your account for Egencia. This travel is for company purposes, and is paid for by the company at the time of booking. For more information on setting up your account please visit our travel page.

Add yourself to the team page

We are happy to have you join our company and to include you in our team page. The following are the steps to add yourself to the team page. Please follow the links that will guide you to full guides about every step. If you are not familiar with local git yet, feel free to do this through the web interface, and ask anyone at the company questions along the way.

Add on GitLab.com
  1. As part of your onboarding issue, you created an account on GitLab.com. take note of your username and password, because you will need them throughout these steps.
  2. You should have been granted access to the www-gitlab-com project as an earlier step of onboarding.
  3. You need to follow the GitLab Workflow to complete this task.
  4. Find the picture that you’d like to add to our team page, change the picture's name to the following format: yourname.jpg or yourname.png and then follow the "how to add an image" steps. Picture Notes:
    • Ensure the picture size is around 400x400 (it must be square) and the format is JPEG or PNG. You can resize your picture using a photo editor like GIMP (cross-platform) or online by searching for "image resize".
    • Any picture that you provide will be made black-and-white automatically after you add it.
  5. In GitLab.com, select the GitLab.com/www-gitlab-com project.
  6. Click on "Files".
  7. Select Source, Images, then Team.
  8. At the top of the page select “+” and upload the file. Note that your team page picture should be added to www-gitlab-com/source/images/team/NAME-OF-PERSON-IN-LOWERCASE.jpg.
  9. Commit these changes with a specific commit message “add NAME to team page” and a unique branch. Remember the branch name as you will use it in the following steps.
  10. Create a Merge Request in GitLab.com with the branch that you created with your picture.
  11. Find the dropdown menu at the top of your screen and find the branch that you previously created to add your picture (they are in alphabetical order).
  12. Go back to the GitLab.com project. Information displayed on Team page is pulled from a data file. You can find it by clicking on each of the following items: Files, data/, and then team.yml.
  13. When you are in team.yml, click on “edit” on the top right side of your screen.
  14. Your information should already be added after the last person on the team page. Update the initials to be your Firstname 'Nickname' Lastname. Verify that your title is entered correctly. Add the filename of the picture that you uploaded previously. Enter your twitter and gitlab handle. Write a story about yourself. Don't forget to use other team members' information as a reference and to respect the spaces between lines. Please don't use "tab" because it will break the page format.
  15. After you added your information, add a comment to your commit and click on “Commit Changes”.
  16. Go to the Merge Request that you previously created with the branch that you are using and assign it to your manager for review.
Add Locally
  1. As part of your onboarding issue, you created an account on GitLab.com. Take note of your username and password, because you will need them throughout these steps.
  2. You should have been granted access to the www-gitlab-com project as an earlier step of onboarding.
  3. You need to follow the GitLab Workflow to complete this task.
  4. Download Git, following the start using git documentation. Don't forget to add your Git username and to set your email.
  5. Follow the steps to create and add your SSH keys.
    Note: in some of these steps, your shell will require you to add your GitLab.com username and password.
  6. Clone the www-gitlab-com project through your shell, following the command line commands documentation.
  7. Create and checkout a new branch for the changes you will be making.
  8. Find the picture that you’d like to add to our team page, change the picture's name to the following format: yourname.jpg or yourname.png and then add it to the source/images/team/ directory. Picture Notes:
    • Ensure the picture size is around 400x400 (it must be square) and the format is JPEG or PNG. You can resize your picture using a photo editor like GIMP (cross-platform) or online by searching for "image resize".
    • Any picture that you provide will be made black-and-white automatically after you add it.
  9. Add the picture so it is staged for commit.
  10. Information displayed on the Team page is pulled from data/team.yml.
  11. Your information should already be added after the last person on the team page. Update the initials to be your Firstname 'Nickname' Lastname. Verify that your title is entered correctly. Add the file name of the picture that you uploaded previously. Enter your twitter and GitLab handle. Write a story about yourself. Don't forget to use other team members' information as a reference and to respect the spaces between lines. Please don't use "tab" because it will break the page format.
  12. After you added your information and saved your changes, add the file to be staged for commit.
  13. To see your changes locally, follow the directions in README.md.
  14. After validating your changes, commit your changes with a comment and push your branch.
  15. Create a Merge Request in GitLab.com with the branch that you created. Assign it to your manager for review.

Reading the Handbook

A core value of GitLab is documentation. Therefore, everything that we do, we have documented on about.gitlab.com. This can make the handbook seem huge! Don't let it scare you. To simplify navigating the handbook here are some suggested steps. Feel free to take a wrong turn at any time to learn more about whatever you are interested in.

  1. Read about the company, and How we use GitLab to build GitLab. It is important to understand our culture, and how the organization was started. If you have any questions about company products you can always check out our features and products.
  2. Tackle general section of the handbook. Here are some highlights that are important for new hires to pay attention to:
    • Make sure to read over our values and general guidelines to answer any questions you might have about what to do and when.
    • If you have questions about what is in the handbook check out the handbook usage as well as your own department's sub-page of the handbook (which can be found at the top of the handbook).
    • Communication is extremely important within a remote only organization. Read through the guidelines to understand how we make working remotely successful.
    • Don't forget to comply with the contract you signed, and make sure you understand Intellectual Property.
  3. Since we are a global organization understand your benefits might be different than other team members at the company based on which contract you signed. It is important to understand your benefits. If you have questions please reach out to People Ops.
    • Notable Benefits that apply to all team members:
    1. No ask time off policy: GitLab truly does value a work-life balance, and encourages team members to have a flexible schedule and take vacations. If you feel uncomfortable about taking time off, or are not sure how much time to take off throughout the year, feel free to speak with your manager or People Operations. We will be happy to reinforce this policy! Please note the additional steps that might need to be taken if you are scheduled for on call.
    2. Check out People Operations to learn more about our policies.
    3. As part of onboarding, you received an email asking if you needed any equipment. Throughout your time at GitLab you might need additional equipment, would like to learn how to code, or want to visit a team member! Make sure you know what you can spend company money on.
    4. The handbook also describes incentives such as sales, dinners, or bonuses, that can apply to all GitLab team members. Know any great talent to refer?
  4. Even if you come from a technical background, it is important to understand the proper workflow since this is how we are all able to operate remotely in a successful way. If you come from a non-technical background, and would like more clarification on what this workflow means, feel free to ask People Ops, your manager, or anyone else at the company.

Learning Git and GitLab

If you need any help with Git itself, subscribe to the #git-help channel on Slack and feel free to ask any question you might have.

Becoming Familiar with Projects on GitLab.com
Learn how to use Git Locally

Learn how to get started with git. It is important for all team members to understand how to work on the Web UI and locally. The rest of the team is happy to assist in teaching you git.

Questions?

At any time if you have questions, please ask your manager, buddy, People Ops, or anyone else at the company!

Please add to me. Questions that were not answered? Something that is not clear? Please create an issue or a merge request and assign it to People Ops to make this documentation better for the next new team member.

Master Checklist for Onboarding of New Hires

Create a new confidential issue for new hire in organization using the onboarding template from the dropdown. The topics are ordered by priority in which they need to be tackled, and the main person responsible is called out at the beginning of each task. Please update the list as more steps arise, and then also update the associated item on the offboarding list.

Quiz

Employees should answer GitLab quiz questions in the first 2 weeks of working in the company. If the answers are not accurate, you may retest once: GitLab Quiz Please schedule a call with your manager.

60-day Onboarding Survey

Please see the NPS section of our handbook.