NCS General Onboarding

Getting started¶

Recommended Training¶

• IT Security Awareness log in into myCourses and click Register on the right side of the page, under Self-Registration courses.

Required Training¶

• ITSM
• Project Online

McGill Perks (Optional)¶

• French at Work
• Staff Fitness
• LinkedIn Learning (Pilot Project)

Project work¶

All gitlab projects and changes required by them should follow a specific process. (Note: This process assumes that you have already cloned the project repository from Master)

1. An issue should be raised in relation to a project, to detail the problem that needs solving/the feature to be added (the work to be done).
2. An issue should be
   • A; Specific (It should be clear what the issue is and what needs to be done to address it)
   • B; Narrow in scope (Merge requests are at their best when short and to the point. This reduces the overhead for code reviews and decreases the likelihood that your work will conflict)
3. Once the issue exists and you are ready to begin work, a Merge Request should be created. This serves to;
4. Create a new branch in which your work will not impact live services
5. Automatically create a merge request to merge your changes into Master
6. git fetch the project locally, then git checkout <branch name> (The exact syntax for each one can be found on the Merge Request under 'Check out Branch')
7. Complete your changes locally and be sure to make your commits using Conventional Commit standards (Note: This is project dependent and though this will be the advised method for most projects, always review the project's CONTRIBUTING.md file where available)
8. If your work has been pushed to the branch and is ready to be merged, go to the merge request and click 'resolve WIP'. You will then need to assign your Merge Request for peer review and merge (project dependent)