Computer Science Question

SWE 442: Software Configuration Management Assignment [CLO 2.1, 2.2, 2.3] (5 points) Due Date: Tuesday, May 7, 2024 at 11.45 p.m. GitHub Repository Setup and Version Control Basics Note: This is an individual assignment. Each student should work individually. Objective: The objective of this assignment is to familiarize students with GitHub’s collaboration features, including forking, cloning, branching, committing, and pull requests. Tasks: 0. Before Starting: ● If you do not have a GitHub account, go to GitHub.com and create one. 1. Forking a Repository: ● Fork the repository “AlmaeenM/SalaryCalculator (github.com)” to your GitHub account. 2. Cloning the Forked Repository: ● Clone the forked repository to your local machine using Git. 3. Branch Creation and Editing: ● Create a new branch named “update-readme” in your local repository. ● Edit the README.md file in your branch to include a brief description of SalaryCalculator.Java 4. Committing Changes: ● Stage and commit the changes made to the README.md file in your branch. ● Write a descriptive commit message. 5. Pushing Changes: ● Push the committed changes to the branch “feature/update-readme” in your forked repository on GitHub. 6. Pull Request: ● Navigate to your forked repository on GitHub. ● Create a pull request (PR) to merge your “feature/update-readme” branch into the main branch of the original repository. ● Include a meaningful title and description for the PR summarizing the changes. 7. Review and Merge: ● Request a review from a classmate or instructor (if applicable) for your PR. ● Once approved, merge the PR into the main branch of the original repository. Submission Guidelines: In a PDF file submit the following: ● Provide the GitHub URL of your forked repository. ● Include screenshots or a summary of the PR and merge process on GitHub. ● Write a brief reflection on your experience with GitHub collaboration and version control.