REST APIs with Flask and Python - Working with Git and Automatic Deploys

This video tutorial covers a workflow for using Heroku with automated deployments. It explains how to set up automatic deploys from GitHub, manage branches effectively, and ensure that the master branch remains stable. The tutorial demonstrates creating feature branches, committing and pushing changes, and merging them back into the master branch to trigger deployments. It emphasizes the importance of keeping the master branch clean and suggests using a production branch for deployments. The video concludes with a preview of deploying to a personal server.

What is the primary reason for enabling automated deployments on Heroku?

• To reduce server costs

• To ensure the app is always working after a commit

• To allow multiple users to access the app simultaneously

• To increase the speed of the application

Why should you avoid working directly on the master branch?

• It requires additional permissions

• It is more difficult to merge changes

• It is reserved for production code

• It can lead to untested code being deployed

What command is used to create a new branch in Git?

• git new branch

• git create branch

• git init branch

• git branch

What should you do after merging a feature branch into the master branch?

• Push the changes to the remote repository

• Continue working on the feature branch

• Delete the master branch

• Create a new repository

What is the purpose of deleting a feature branch after merging?

• To allow more users to access the branch

• To save storage space

• To prevent further commits to that branch

• To increase the speed of the application

What is a common practice to keep the master branch clean?

• Avoid using branches

• Only merge tested and working code

• Merge all changes immediately

• Commit directly to master

What alternative branch can be used for deployments instead of master?

• Production

• Staging

• Testing

• Development