These are challenges for practicing the concepts we talked about in our training (Git & GitHub training)
To have the best results, don't hurry and carefully read each challenge. Make sure you solve them in order:
- Fork this repo
clone
the repo on your PC- Add a new cell into the grid from prep.html and write your name or nickname in there.
- Add a new commit following the convention:
[username] - description
. - Push those changes on master
- Add a photo of youself inside the
assets/participants
folder. Let's name it after yourusername
. - Add that photo to the cell from step 3.
- Add one commit for each modified file. Let's keep the same convention as last time:
[username] - description
. - Push both commits on master.
- Create a new branch from master named prep-challenges
--- From now on work on this new branch
- Add in prep.html a new cell with a description of yourself.
commit
andpush
this new cell.- Add one of the trainers as a contributor in your project
- The trainer will add in prep.html a new cell with a photo of himself/herself.
- Trainer pushes on master directly.
- Create a PR (Pull Request) to add your code in master.
- Fix the merge conflicts
- Merge branch. Now on master will be both descriptions!
- Hooray! You've finished the learning challenges. You can move on to the next which you'll implement on your own.
- Move to the master branch of the repo.
- Create a new branch called vscode.
- Add a new cell into the grid from exercitii.html and write your name or nickname in there.
- Add the "Fill-in info" component in index.html and write your name or nickname in there. (you can find it's markup at the bottom of this page)
- Add one commit for each modified file. Let's keep the same convention as last time:
[username] - description
push
these changes on master- Create a new branch from the current one (vscode) named challenges
--- From now on work on this new branch
- Add in exercitii.html a new cell with a photo of yourself.
commit
andpush
this code. - Add another cell with some short info about yourself. It can be a favorite hobby, your job title, or why you want to learn Git?! After you're done,
commit
andpush
this code as well. - Let's use the "Commands list" component and add a list of all the actions used so far in the grid.
commit
andpush
the new modifications- Add in exercitii.html a new cell with the number of commits you've done so far.
commit
andpush
changes in the remote repo- We're wondering whether instead of the list of actions we should add a description about Git/GitHub. Let's create a new branch named challenges-v2 where we're gonna experiement with this.
--- From now on work on this new branch
push
the branch in the remote repo. Now you should have 3 branches total.revert
the commit with the actions list- Add a small description about Git inside a new cell from exercitii.html. Then
push
in the remote repo - We decide to keep the old version.
- Make a
PR
tovscode
fromchallenges
branch. - After approval, merge it.
- Navigate to
vscode
branch andpull
the changes locally. - Test that everything looks ok.
- Done! 💪
- Create a new branch from master named cli.
- Add a new cell into the grid from exercitii.html and write your name or nickname in there.
- Add the "Fill-in info" component in index.html and write your name or nickname in there. (you can find it's markup at the bottom of this page)
- Add one commit for each modified file. Let's keep the same convention as last time:
[username] - description
push
these changes on cli- Create a new branch named challenges
--- From now on work on this new branch
- Add in exercitii.html a new cell with a photo of yourself.
commit
andpush
this code. - Add another cell with some short info about yourself. It can be a favorite hobby, your job title, or why you want to learn Git?! After you're done,
commit
andpush
this code as well. - Let's use the "Commands list" component and add a list of all the commands used so far in the grid.
commit
the new modifications BUT don't push yet - We're about to use the
amend
command. Let's add this one to the list as well. - We don't want to make another commit. Instead we want to add it to the previous one. Let's run
add
and thencommit --amend
. push
this newly edited commit in the remote repo- Add in exercitii.html a new cell with the number of commits so far.
push
changes in the remote repo- We're wondering whether instead of the list of commands we should add a description about Git/GitHub. Let's create a new branch named challenges-v2 where we're gonna experiement with this.
--- From now on work on this new branch
push
the branch in the remote repo. Now you should have 3 branches total.revert
the commit with the commands list- Add a small description about Git. Then
push
in the remote repo - Connect
GitHub pages
to your new branch from this repo. - Navigate to the deplyed app and see the result so far
- We decide to keep the old version. Let's delete the
challenges-v2
branch fromremote
as well as fromlocal
. - We're ready to merge the
challenges
branch into master. Let's add one of the trainers as a contributor - Make a
PR
to master - After approval, merge it.
- Navigate to
master
andpull
the changes locally. - Test that everything looks ok.
- Change
GitHub pages
to themaster
branch and see your final result deployed.
After trainer approval:
- On master, "navigate back" to the last commit by us. You'll have to use
checkout
. - Create a new branch from here named after your username.
- Add a card with info about yourself in the finalisti.html page.
- Create a PR into the original repo
- We merge & celebrate! 🎉
<ol class="commands-list my-5">
<li>
commit
</li>
<li>
push
</li>
<li>
pull
</li>
</ol>
<div class="fill-in-info">
<label>
Numele meu:
</label>
<p>
Jon Doe
</p>
</div>