Exam V
Adding a message to a commit is discouraged
False
GitHub is a version control system
False
I fork a repository. This keeps all issues and pull requests from the original repository.
False
If you don't need to sync with the original repository, and just want to play with the code, you should fork instead of clone
False
If you want to collaborate and keep the link to the original repository, we clone instead of fork
False
In order to create a repository on GitHub called 'example', we use the command 'git github add example'
False
In order to create a repository with a connection to GitHub, you must create the repository locally first
False
To clone a repository, it is best to first use git init to create a repository, and then clone within it
False
To create a repo that has a connection to GitHub, you must create the repository on GitHub first
False
We don't need GitHub to use git. This is also true for forking.
False
When we merge from our local machine, it simultaneously updates GitHub
False
When you fork a repository, it keeps all the information from the original repository, just like when you clone
False
You mostly create .gitignore files yourself so you can keep track of the files you're ignoring
False
git log allows you to create a report of your recent changes to code, and you create that log in any text editor
False
A .gitignore file lets you not track certain files that very frequently are unnecessary to track
True
Changes to git projects can be made asynchronously
True
I make changes to a file and add it to the staging area. I make further changes to that file. If I want to commit the most updated version, I need to re-add the file to the staging area.
True
If you do not add a message to a commit, a prompt will ask you for one
True
In order to push a cloned repository, we'd first create our own repository on GitHub to push to
True
One advantage of version control is that it allows a collaborators to see a transparent history of changes, who made them, and how they contribute to the development of a project
True
The purpose of a pull request is to collaborate with others, generally telling them you've made changes to a branch
True
You will often get a .gitignore file straight from GitHub
True
Which of the following does Git keep track of?
What changes are made Who made the changes When changes were made Why the changes were needed
When you work on a project, you're going to have a bunch of different features or ideas in progress at a given time. Those features can be worked on without disrupting your main code by creating and working on a
branch
You have a file called "readme.md" and want to put it in the staging area. What command does this?
git add readme.md
How would you make a commit with the message 'add readme'?
git commit -m 'add readme.md'
Which of the following is NOT a git command?
git create
How would you create a repository called "mydirectory"?
git init mydirectory
To merge with the master branch, we leave the branch we've updated by using git
merge main
A ______ contains files, folders, and revision history associated with a project
repository
If we clone a repository and change the remote to our own, but want to keep a connection to the original repository, by convention we refer to that remote as
upstream