Небольшой проект по использованию технологии GIT

Нужно провести некоторые действия с репозиториями через командную строку и поделиться решением задания, а именно используемыми командами

Образцы изначальных репозиториев есть, задание видно на скриншотах, которые приложены к этому заданию

Краткое описание задания на англйиском :

First, let’s clear the history of the Alice repository:

Create a local branch alice from the alice/master branch.
Commit fix script issues contains only minor edits, so you want to meld it into a correct commit using a fixup operation. Unfortunately, the commit is not created as a fixup! one, so you have to find manually an earlier commit that modifies the same file (hint: there is only one such commit). Meld the commits with a suitable edit history operation.
Now the alice branch should contain 8 commits. Note that no further edits are needed (these commits already have the correct authors and titles), push the branch to the server.

Bob was trying to keep up with Alice’s repository, therefore, was creating a large number of merge commits. Additionally, we have yet to decide if Bob’s calendar peeking is a release-ready feature. Therefore, we need to clean up his branch as well first:

Create a local branch bob from the bob/master branch.
Use rebase (and other appropriate switches) to rebase this branch over the current state of the local alice branch. Some hints:
The branch also contains some (properly created) fixup! commits that you want to meld into the correct commits.
Also note that the rebase TODO list includes commits whose changes are already contained in the alice branch (and are not related to the ical component), remove these commits from the list.
To be sure, we recommend opening the repository graph in a second terminal and checking the changes brought by each commit.
Maybe a quick explanation of the source of these items in the TODO list will help:
some are the result of modifying the alice branch in the previous steps and
some commits are the result of bad timing, where Bob merged in Alice’s repository just before Alice joined up her fixup! commit and force-pushed.
After these operations, there should be six new commits in the bob branch (i.e., on top of the alice branch).
Checkpoint: create a bob_dirty branch from the current state and push to the server. 
Some commits in the bob branch have a bad commit message format. Since they all refer to the ical component now, add the component name as a prefix, separate with a colon and space, and edit the first letter of the title to be uppercase (e.g., ical: Introduce ical_peek to dfi).
Checkpoint: create a bob_title branch from the current state and push to the server.
Next, you’ll notice that the src/ical_peek/test/events.ics and src/ical_peek/test/events.ics.peek files contain personal information about Monica’s birthday that has no place in the repository. Find the commit where the event was added to the test calendar (and the corresponding output), and remove the entire event from the .ics file (the event is delimited by BEGIN:VEVENT and END:VEVENT) and the script output line from .peek.
After further discussion with colleagues, you conclude that this component is ready for release, so mark the current state as a new master branch (which is currently missing in the repository) and push to the server.