Skip to content

Module 4 challenge: Push local commits to Github :Introduction to Git and GitHub (Google IT Automation with Python Professional Certificate) Answers 2025

1. Effect on remote repository after local changes
❌ The remote repository duplicates your local changes without you pushing
✔️ The remote repository remains unchanged until you push
❌ The remote repository is deleted
❌ The remote repository is automatically updated

2. Command to check Git repository states
❌ git update
❌ git repo-status
❌ git check
✔️ git status

3. Importance of descriptive commit messages
❌ To reduce the size of the commit
❌ To make the commit process faster
✔️ To help other developers understand the changes
❌ To allow the system to automatically sort commits

4. Primary purpose of a pull request
❌ To merge changes from the local branch to the remote repository without review
❌ To revert the changes made in a specific branch
❌ To create a new branch in the remote repository
✔️ To propose changes and initiate a discussion before merging them into a branch

5. Branch after a pull request is merged
❌ It is automatically deleted
❌ It is locked and cannot be changed
✔️ It remains available for further work
❌ It becomes the main branch

6. Main benefit of using pull requests
❌ To automatically merge changes from one branch to another
❌ To revert changes made in a branch back to a previous commit
❌ To create a backup of the repository before making changes
✔️ To propose changes, facilitate code review, and ensure quality before merging them into the target branch

7. Purpose of “Conversation” tab in GitHub pull request
✔️ Discussion and comments
❌ Real-time code execution
❌ Code review approval
❌ Code formatting

8. Actions during a code review (select all that apply)
✔️ Provide constructive feedback
❌ Accept all changes
✔️ Skim the code for major mistakes
✔️ Offer suggestions for improvements

9. Importance of reviewing code before merging
✔️ To find and fix potential bugs and ensure the code aligns with the project’s standards
❌ To make the author feel bad about their code
❌ To make sure the code is perfect
❌ Because it’s a requirement

10. Primary purpose of creating a fork of a repository
❌ To create a backup copy of the original repository
❌ To permanently remove the original repository
✔️ To contribute changes to the original repository through pull requests
❌ To privatize the repository and make it inaccessible to others


📌 Summary Table

Q# Correct Answer(s)
1 Remote unchanged until push ✔️
2 git status ✔️
3 Help others understand changes ✔️
4 Propose changes & discussion before merge ✔️
5 Branch remains available ✔️
6 Propose changes & code review ✔️
7 Discussion and comments ✔️
8 Constructive feedback ✔️, skim for mistakes ✔️, suggest improvements ✔️
9 Find/fix bugs & ensure standards ✔️
10 Contribute changes via pull requests ✔️