YDM3 YDM3 Task 1: Version Control Using Git for GitLab

Competencies

4072.1.1 : Implements Version Control

The learner implements version control processes and solutions that maintains source code.

Introduction

Version control, also referred to as revision control or source control (i.e., git), is an efficient way of managing changes to files over time. Managing files over time enables teams to collaborate freely because members can work on the same file at the same time and merge changes later. Version control and version control systems can be leveraged by anyone in an organization, from the development team to the software testing teams and even the product development/design team.

For this assessment, you will use the given scenario to create a GitLab repository and submit the link to it along with screenshots showing the work completed.

Before starting your work, review the “GitLab How-To” web link. Then, use the “GitLab” link to obtain the template. You will clone your GitLab repository to your computer to create a local repository. You will be modifying your local repository using Git Bash (Windows users) or using the Mac terminal (macOS users).

Scenario

You have been hired as a consultant at a company. The company has a collection of files for its website that need modification to complete the project deliverables. However, the company’s contract requires that all documents be saved to a source repository, and there are other consultants working concurrently. You have been asked to make upgrades to the website.

Requirements

Your submission must represent your original work and understanding of the course material. Most performance assessment submissions are automatically scanned through the WGU similarity checker. Students are strongly encouraged to wait for the similarity report to generate after uploading their work and then review it to ensure Academic Authenticity guidelines are met before submitting the file for evaluation. See for more information.

Grammarly Note:
Professional Communication will be automatically assessed through Grammarly for Education in most performance assessments before a student submits work for evaluation. Students are strongly encouraged to review the Grammarly for Education feedback prior to submitting work for evaluation, as the overall submission will not pass without this aspect passing. See for more information.

Microsoft Files Note:
Write your paper in Microsoft Word (.doc or .docx) unless another Microsoft product, or pdf, is specified in the task directions.Tasks maynotbe submitted as cloud links, such as links to Google Docs, Google Slides, OneDrive, etc. All supporting documentation, such as screenshots and proof of experience, should be collected in a pdf file and submitted separately from the main file.For more information, please see

You must use the rubric to direct the creation of your submission because it provides detailed criteria that will be used to evaluate your work. Each requirement below may be evaluated by more than one rubric aspect. The rubric aspect titles may contain hyperlinks to relevant portions of the course.

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 GitLab

A. Create your subgroup and project in GitLab 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.

2. Include a screenshot of your current repository graph in GitLab.

Clone Your Repository on Your Local Machine

B. 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 Push

C. 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.

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 Change

D. Modify a file on a new branch in your local repository by doing the following:

1. Include a screenshot of the current repository graph in GitLab after pushing the changes.

Simulate a Merge Conflict

E. Introduce a merge conflict with the “Test” branch by doing the following:

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 Branch

F. Specify a version for your local repository by doing the following:

1. Include a screenshot of the current repository graph in GitLab.

Add a Retrospective Directory to Repository

G. Add retrospective information by doing the following:

1. Create a directory on the Working branch named “retrospective”.

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.

3. Create a “summary.txt” file in the retrospective directory and include the following:

4. Create one file (PDF or Word document) that contains all screenshots and comments from parts AF and place the file in the retrospective directory.

5. Push all changes made in parts G1G4 to GitLab.

Final Step

H. Include the repository link to your GitLab in the “Comments to Evaluator” section when you submit this assessment.

I. Demonstrate professional communication in the content and presentation of your submission.

File Restrictions

File name may contain only letters, numbers, spaces, and these symbols: ! – _ . * ‘ ( )
File size limit: 200 MB
File types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt, pdf, csv, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, flv, asf, mpeg, wmv, m4v, svg, tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7z