This repository has been archived by the owner on Oct 25, 2024. It is now read-only.
This repository has been archived by the owner on Oct 25, 2024. It is now read-only.
Practising branches with git (optional) #14
Open
Description
Exercise A - Creating a feature branch for my_pipeline
Using your my_pipeline
repository, you'll create a new branch called complex-steps
, do some work on it, and then merge it back into your main
branch
- On your terminal, within your
my_pipeline
repository create and switch to a new branch calledcomplex-steps
- Modify
readme.md
with some more workflow steps - Check the status, then add and commit as usual
- Push your branch to your remote on Github (e.g.
git push -u origin complex-steps
) - Switch back to your
main
branch - look at the contents ofreadme.md
- Still on your
main
branch - modify the steps inreadme.md
, add and commit. - Run
git log --all --decorate --oneline --graph
and have a look at the output - Merge your
complex-steps
branch into yourmain
branch - Fix any conflicts, add, and commit
- Run
git log --all --decorate --oneline --graph
again and observe what the output is.
Exercise B - A Complex Branch Structure
In small groups or individually, using Github's visualisation tool as shown in class, do the steps needed to replicate the repository structure shown below.
❗ hash numbers for the commit are going to be different and the final shape of the graph may look slightly different.
Metadata
Assignees
Labels
No labels