Create a repository by doing the following:Note: Screenshots should include the git response from the command prompt or the entire graph window.Note: All operations should be performed on your local machine using Git Bash or another shell unless GitLab is specifically mentioned.Note: You may commit and push at any time, even if a task is not complete.Prepare Your Repository with Initial Data on GitLabA. Create your subgroup and project in Git Lab using the provided web link and the "GitLab How$-$To$"$ web link by doing the following:$1.$ Create a new branch named "Working" in GitLab$\mathrm{.}2.$ Include a screenshot of your current repository graph in GitLab.Clone Your Repository on Your Local MachineB. Clone your remote repository from GitLab to your local machine using the command line interface. Include a screenshot of the command line action and be sure to have your repository name visible in the command prompt.Make Changes, Commit, and PushC. Modify $($using any text editor$)$ three HTML files on the Working branch by doing the following:$1.$ Commit each change with a short, meaningful message that explains all changes you have made to the three HTML files. Include a screenshot for each git command for each change and be sure to have your repository name visible in the command prompt$\mathrm{.}2.$ Push the branch to GitLab. Include a screenshot of the command line action and be sure to have your repository name visible in the command prompt.Create a New Branch and Make a ChangeD. Modify a file on a new branch in your local repository by doing the following:$*$ create a "Test" branch using the command line interface$*$ add your student ID to the README.md file$*$ push the changes to the remote repository in GitLab$*$ include a screenshot of the command line action and be sure to have your repository name visible in the command prompt$1.$ Include a screenshot of the current repository graph in Git Lab after pushing the changes.Simulate a Merge ConflictE. Introduce a merge conflict with the "Test" branch by doing the following:$*$ add the git version number to the READMEmd file on the Working branch$*$ merge the "Test" branch to the Working branch in your local repository$*$ include a screenshot that demonstrates the conflict of this merge command line action and be sure to have your repository name visible in the command prompt$1.$ Resolve the created conflict and push the changes to the Working branch in GitLab. Include a screenshot of the current repository graph in GitLab.Tag a BranchF. Specify a version for your local repository by doing the following:$*$ tag the Working branch as version V$\mathrm{.}1\mathrm{.}0\mathrm{.}0*$ push the tag to GitLab$*$ include a screenshot of the command line action and be sure to have your repository name visible in the command prompt$1.$ Include a screenshot of the current repository graph in GitLab.Add a Retrospective Directory to RepositoryG. Add retrospective information by doing the following:$1.$ Create a directory on the Working branch named "retrospective"$\mathrm{.}2.$ Create a log$.$txt that will contain the output of the git log command in the retrospective directory.Note: Use "git log $>$ log$.$txt$"$ to redirect output to the file$\mathrm{.}3.$ Create a "summary.txt$"$ file in the retrospective directory and include the following:$*$ summarize how the merge conflict in part E$1$ was resolved$*$ describe the three changes that you made in part C$11.$ Create one file $($PDF or Word document$)$ that contains all screenshots and comments from parts A$-$F and place the file in the retrospective directory$\mathrm{.}2.$ Push all changes made in parts G$1-$G$4$ to GitLab.Final StepH. Include the repository link to your GitLab in the "Comments to Evaluator" section when you submit this assessment$\mathrm{.}1.$ Demonstrate professional communication in the content and presentation of your submission