Module 03 · Final Project and Assessment最终项目与评估

Peer-graded Assignment: Final Project: Submit Your Work and Review Your Peers同伴互评作业：最终项目提交与同伴评审

Prior to submitting your work and reviewing your peers', please ensure you have completed the hands-on labs portion of the project.
在提交您的作品并审阅同行的作品之前，请确保您已经完成了项目的动手实验室部分。

There are a total of 20 points for 10 tasks in this final project spread across two hands-on labs. Your final assignment will be graded by your peers who are also completing this assignment within the same session. You need to submit the following item for peer review, and the exact format is specified in each task.
本最终项目共有 10 个任务，共计 20 分，分布在两个实践实验室中。你的最终作业将由同样在本会话中完成此作业的同学们进行评分。你需要提交以下项目供同学评审，每个任务中都有具体的格式要求。

A URL submission for 4 tasks
一个 URL 提交用于 4 个任务
A text submission for 5 tasks
一份针对 5 个任务的文本提交
A screenshot submission for 1 task
截图提交，1 个任务

These will link to your project for your peers to review.
这些将链接到您的项目，供您的同行审阅。

Grading Criteria Overview 评分标准概述

Grading Criteria – 20 marks total
评分标准 - 总计 20 分

The final assignment grading criteria for the two parts are as follows:
最终两个部分的作业评分标准如下：

Part 1 GitHub UI (12 points)
第一部分 GitHub UI（12 点）

Task 1: Submit the URL of the repository. (2 pts)
任务 1：提交仓库的 URL。（2 分）
- 0 pts: No URL is submitted.
  0 分：未提交 URL。
- 1 pt: Valid URL submitted but the URL is empty.
  1 pt：有效的 URL 已提交，但 URL 为空。
- 2 pts: Valid URL submitted, and the URL has all the files as expected.
  2 分：提交了有效的 URL，且 URL 包含所有预期的文件。
Task 2: Apache 2.0 License file named LICENSE is present in the repository. (2 pts)
任务 2：仓库中存在名为 LICENSE 的 Apache 2.0 许可证文件。（2 分）
- 0 pts: The repository doesn't have a license file.
  0 分：仓库中没有许可证文件。
- 1 pt: The repository has a license file, which is different from the specification.
  1 pt：存储库有一个许可证文件，这与规范不同。
- 2 pts: The repository has Apache 2.0 license file.
  2 分：仓库包含 Apache 2.0 许可文件。
Task 3: README.md file is present in the repository. (2 pts)
任务 3：README.md 文件存在于仓库中。（2 分）
- 0 pts: The repository doesn't have a README file.
  0 分：仓库中没有 README 文件。
- 1 pt: The repository has a README file, which is different from the specification or has no content.
  1 pt：仓库中有一个 README 文件，与规范不同或没有内容。
- 2 pts: The repository has README.md file as per specification.
  2 分：仓库按照规范包含 README.md 文件。
Task 4: CODE_OF_CONDUCT file is present in the repository. (2 pts)
任务 4：行为准则文件存在于仓库中。（2 分）
- 0 pts: The repository doesn't have a CODE_OF_CONDUCT.md file.
  0 分：仓库中没有 CODE_OF_CONDUCT.md 文件。
- 1 pt: The repository has a CODE_OF_CONDUCT file, which is different from the specification or has no content.
  1 pt：仓库中有一个 CODE_OF_CONDUCT 文件，与规范不同或没有内容。
- 2 pts: The repository has CODE_OF_CONDUCT file as per specification.
  2 分：仓库按照规范包含 CODE_OF_CONDUCT 文件。
Task 5: CONTRIBUTING.md file is present in the repository. (2 pts)
任务 5：CONTRIBUTING.md 文件存在于仓库中。（2 分）
- 0 pts: The repository doesn’t have a CONTRIBUTING.md file.
  0 分：仓库中没有 CONTRIBUTING.md 文件。
- 1 pt: The repository has a CONTRIBUTING file, which is different from the specification or has no content.
  1 pt：仓库中有一个 CONTRIBUTING 文件，与规范不同或没有内容。
- 2 pts: The repository has a CONTRIBUTING file as per specification.
  2 分：仓库按照规范包含一个 CONTRIBUTING 文件。
Task 6: The file simple-interest.sh is present in the repository. (2 pts)
任务 6：文件 simple-interest.sh 存在于仓库中。（2 分）
- 0 pts: The repository doesn't have a simple-interest.sh file.
  0 分：仓库中没有 simple-interest.sh 文件。
- 1 pt: The repository has a simple-interest.sh file, which is different from the specification or has no content.
  1 pt：仓库中有一个 simple-interest.sh 文件，与规范不同或没有内容。
- 2 pts: The repository has a simple-interest.sh file as per specification.
  2 分：根据规范，仓库中有一个 simple-interest.sh 文件。

Part 2 Git CLI (8 points)
第二部分 Git 命令行界面（8 分）

Task 1: Submit the URL of the forked repository. (2 pts)
任务 1：提交分叉仓库的 URL。（2 分）
- 0 pts: The URL is not submitted or the link doesn't work.
  0 分：URL 未提交或链接无法工作。
- 1 pt: The URL is a valid link, but the contents are not forked correctly.
  1 pt：URL 链接有效，但内容未正确分支。
- 2 pts: The URL is a valid link and is the fork of the given repository with all the contents.
  2 分：该 URL 是一个有效的链接，并且是给定仓库的分支，包含所有内容。
Task 2: Submit the screenshot of the first merge. (2 pts)
任务 2：提交第一次合并的截图。（2 分）
- 0 pts: The image is not submitted.
  0 分：图片未提交。
- 1 pt: The image submitted shows that the branch bug-fix-typo is merged onto main but the details are not fully correct.
  1 pt：提交的图片显示，分支 bug-fix-typo 已合并到主分支，但细节并不完全正确。
- 2 pts: The image shows that the current branch is main and changes to README.md file in bug-fix-typo have been merged to main.
  2 分：图中显示当前分支为主分支，bug-fix-typo 中的 README.md 文件更改已合并到主分支。
Task 3: Submit the URL of the pull request. (2 pts)
任务 3：提交拉取请求的 URL。（2 分）
- 0 pts: The URL is not submitted.
  0 分：URL 未提交。
- 1 pt: The URL works but doesn't point to the pull request.
  1 pt：URL 可以工作，但并未指向拉取请求。
- 2 pts: The URL works and reflects the pull requested which has been accepted.
  2 分：URL 正常工作并反映了已接受的拉取请求。
Task 4: Submit the URL of the Branches page displaying the branch names and their status in your repository. (2 pts)
任务 4：提交显示分支名称及其状态的分支页面 URL。（2 分）
- 0 pts: The URL is not submitted.
  0 分：URL 未提交。
- 1 pt: The URL just shows the number of branches as 3 viz (main, bug-fix-typo and bug-fix-revert), but the details are not evident.
  1 pt：URL 仅显示分支数量为 3，即（主分支、bug-fix-typo 和 bug-fix-revert），但细节并不明显。
- 2 pts: The URL shows the branch names and the status.
  2 分：URL 显示分支名称和状态。