29 Questions
What is the next step after making sure all the commits of your branch are pushed to the origin?
Create a new pull request on Github
Where can you find the option to 'Compare & pull request' when creating a new pull request?
On the 'Code' page
What should be the 'base branch' when creating a pull request to merge your functionality?
Main
What does choosing the 'Squash and merge' option do when merging your code?
Gathers all commits into one for better readability
What should you do if your commit message is generated automatically and includes spelling errors?
Review and fix any spelling errors
How many rounds of review might be needed before your code is considered mergeable?
Several rounds of review
What is a crucial reason for maintaining a clean repository?
To prevent bugs from being pushed to production
When is it advisable to ask for help from a team member during the Git process?
When in doubt at any point
What is the caution given about force-pushing to the remote repository (origin)?
Never force-push to the origin
Why should you be cautious when force-pushing changes to a branch?
To avoid irreversible damages
What is the significance of rebasing main into your-functionality in Git workflow?
Aligning your branch with the latest changes in the main branch
What should you avoid doing when committing changes in Git workflow?
Committing directly to the production branch
What type of branch should you commit to instead of committing directly to the main branch?
A branch specific to the functionality you're developing
When should you commit your code according to the text?
Whenever a small part of your work is done
What should the message of your commit start with, based on the text?
A verb
What should you check before committing your code?
Use the 'git status' command
What is a Pull Request on Github used for?
To review and merge code changes
Who should review your code before it is merged?
Less experienced developers should also review it
What is the correct Git command to push after a successful rebase?
git push --force-with-lease
What is the recommended action when a PR needs to be merged into main without prior review?
Merge the PR and add the tag '🙏 review'
How should developers handle an already merged PR that needs further changes?
Reopen the PR, checkout to the related branch, rebase main, and make requested changes
What should a reviewer do after finding no issues with an already merged PR?
Remove the '🙏 review' tag
What action should be taken when comments are made on an already merged PR for requested changes?
Reopen the PR, checkout to the branch, rebase main, and address the comments
What is recommended when providing comments on others' work?
Use emojis to soften the message
What is the purpose of using 'git pull --rebase'?
To combine the changes fetched from the remote repository with your local changes
When would you consider using rebase according to the text?
When your code needs to include changes pushed to the main branch
What does 'git pull --rebase=merges origin main' command do?
Fetches changes from 'main' branch and rebases them onto your current branch
What should you ensure before starting a rebase operation as per the text?
Your functionality branch is up-to-date with the origin
Why might conflicts occur during a rebase operation according to the text?
Due to changes made in the remote repository conflicting with your local changes
Test your knowledge on Git workflow, including topics like creating a pull request, reviewing a pull request, rebasing changes, and maintaining a clean repository. The quiz covers essential steps to follow in daily workflow and provides insights on merging PRs.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
