Git for Organisations
Course Level: Intermediate (6 hours)
Git is perfect for working collaboratively. However, when you’re working together in an organisation, it’s important to have rules and processes so you all know how to work together. We’ll share what works for us at Jumping Rivers, and then guide you through the process of coming up with your own rules and processes for git, such as choosing a branching strategy and formalising your code review.
Book: Git for Organisations
- Start Date:
- Price:
- Venue Details:
- Time:
- Duration:
No Events Currently Scheduled
Sorry, there are no upcoming events for this course, but please get in touch if you would like to be kept informed when events are scheduled in the future.
Course Details
Outline
- Branching workflows and protected branches
- CODEOWNERS and other standard repository files
- Merge requests and code reviews
- Managing Git Issues
- Example git workflows from start to end
Learning Outcomes
Session 1:
By the end of session 1, participants will…
- be familiar with Git Workflows:
- Google “Git Workflow”
- Classic Workflow
- GitHub and GitLab Workflow
- understand the Git Server.
- have knowledge on repositories and its features.
- have explored different associated Git files:
- README.md
- .gitignore
- CODEOWNERS
- be comfortable understanding the uses in Data Science.
- be able to create and use GitLab issues and labels.
- have knowledge on keeping track of projects.
- Issue boards
Session 2:
By the end of session 2, participants will…
- be introduced to cloning a repositories.
- Creating branches
- Applying changes
- Pushing to a remote branch
- Assigning a reviewer
- have knowledge on committing changes.
- be able to create and assign merge requests.
- have created a list of default settings and processes to implement within their own organisation
This course does not include:
- Complex GitLab and GitHub features such as rebasing, stashing commits or editing to the previous commits.
Prior Knowledge
This course assumes basic skills with git, so having attended Git for Me or equivalent is necessary.
Attendee Feedback
- “There was ample opportunity to think and discuss how the suggestions and workflows could be implemented in our own work, "
- “Really knowledgeable presenters”