Use AI With Git for Real Coding Projects

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-builders-ai-coding-AI-and-version-control

1. You want to save your current code changes to the project history but are not ready to share them with your team yet. What Git action would you perform?

   1. Push your changes to the remote repository
   2. Create a new branch for your work
   3. Commit your changes with a descriptive message
   4. Discard all your changes

2. What is a merge conflict in Git?

   1. When two people edit the same part of a file and Git cannot automatically decide which change to keep
   2. When you accidentally delete your entire project
   3. When Git crashes and loses your files
   4. When you try to push to a repository but have no internet connection

3. Your teammate asks you to review their Git commit message that says 'fixed stuff'. Why is this considered a poor commit message?

   1. It does not explain what changed or why the change was needed
   2. It was written in a different language
   3. It uses too many technical words
   4. It is too long and complicated

4. What does version control allow developers to do?

   1. Write code automatically without human input
   2. Create user interfaces for apps
   3. Track every change made to code over time and reverse mistakes if needed
   4. Test if a website loads correctly

5. You just made a commit but realize you want to undo it while keeping your code changes. What should you do?

   1. Commit the changes again with a different message
   2. Use a Git command to reset while preserving your working files
   3. Delete the entire repository and start over
   4. Wait 24 hours for the changes to expire

6. How can AI help someone learning Git?

   1. Automatically write all the code for them
   2. Explain confusing commands and suggest the right ones to use
   3. Run Git commands on their computer without permission
   4. Replace the need to learn version control entirely

7. What is a repository in Git?

   1. A cloud service that hosts websites
   2. A folder that contains your project code and its complete history of changes
   3. A backup of your code saved on a USB drive
   4. A type of computer program that writes code

8. Why do professional coding projects require Git?

   1. Because it makes code run faster
   2. Because it is required by law
   3. Because computers cannot function without it
   4. Because multiple people work on the same code and need to coordinate without overwriting each other

9. What does 'pushing' mean in Git?

   1. Copying code from someone else's project into yours
   2. Sending your committed changes from your local computer to a shared remote server
   3. Running your code to see if it works
   4. Deleting old code that is no longer needed

10. A teammate explains your team uses a 'feature branch workflow.' What does this mean?

    1. All team members work directly on the main branch
    2. Branches are only used for fixing bugs
    3. Features are deleted after being completed
    4. Each new feature gets its own separate branch that is merged when complete

11. What is the main benefit of writing a clear commit message?

    1. Git will work faster
    2. You can skip writing documentation
    3. The code will run without errors
    4. Future developers (including yourself) can understand why changes were made

12. What happens when you 'pull' in Git?

    1. You download the latest changes from a remote repository to your local computer
    2. You create a backup of your code
    3. You test your code for errors
    4. You remove a file from the project

13. Why might a beginner ask AI to help resolve a merge conflict?

    1. Because conflict resolution requires understanding which changes to keep and involves editing files
    2. Because Git automatically fixes all conflicts
    3. Because merge conflicts only happen to beginners
    4. Because AI can delete the conflicting files

14. What does it mean to 'stage' changes in Git?

    1. To test if code works correctly
    2. To send changes to another developer
    3. To permanently delete unwanted files
    4. To mark specific changes to be included in the next commit

15. How does AI make Git less intimidating for new learners?

    1. It explains what unfamiliar commands do and provides examples in plain language
    2. It changes the Git commands to be simpler
    3. It makes Git into a game with no real consequences
    4. It runs all Git commands automatically so learners never need to learn