Domain 2: Working with GitHub Repo's - Deck 1

Question 1

Branch

Answer 1

A parallel version of your code that is contained within the repository, but does not affect the primary or main branch.

Question 2

To download a full copy of a repository’s data from GitHub.com, including all versions of every file and folder.

Answer 2

Clone

Question 3

A new repository that shares code and visibility settings with the original “upstream” repository.

Answer 3

Fork

Question 4

To take the changes from one branch and apply them to another.

Answer 4

Merge

Question 5

A request to merge changes from one branch into another.

Answer 5

Pull request (PR)

Question 6

A repository stored on GitHub, not on your computer.

Answer 6

Remote

Question 7

The branch on an original repository that has been forked or cloned. The corresponding branch on the cloned or forked branch is called the “downstream.”

Answer 7

Upstream

Question 8

what are good components in a README file communicate expectations for your project and helps you to manage contributions.

Answer 8

A README, along with a repository license, citation file, contribution guidelines, and a code of conduct, communicates expectations for your project and helps you manage contributions.

Question 9

the first item a visitor will see when visiting your repository

Answer 9

A README

Question 10

What does a README file typically include

Answer 10

README files typically include information on:

• What the project does
• Why the project is useful
• How users can get started with the project
• Where users can get help with your project
• Who maintains and contributes to the project

Question 11

If the README file is put in these three places

Answer 11

If you put your README file in your repository’s hidden.github,root, ordocsdirectory, GitHub will recognize and automatically surface your README to repository visitors.

Question 12

If a repository contains more than one README file, then the file shown is chosen from locations in the following order:

Answer 12

1. the.githubdirectory
2. the repository’srootdirectory
3. thedocsdirectory

Question 13

Steps to create a new repository

Answer 13

In the upper-right corner of any page, select the dropdown, then click New repository:
1. Use the Owner dropdown menu to select the account you want to own the repository.
2. Type a name for your repository, and an optional description.
3. Choose a repository visibility. For more information, see “About repositories.”
4. You can create a README, which is a document describing your project.
5. You can create a .gitignore file, which is a set of ignore rules.
6. You can choose to add a software license for your project.
7. Click Create repository:

Question 14

Steps to create a template repository

Answer 14

1. On GitHub.com, navigate to the main page of the repository.
2. Under your repository name, click Settings:
3. Select Template repository:

Question 15

Steps to clone a repository

Answer 15

Cloning a repository pulls down a full copy of all the repository data that GitHub.com has at that point in time, including all versions of every file and folder for the project.

To clone a repo, follow these steps:

1. On GitHub.com, navigate to the main page of the repository.
2. Above the list of files, click Code.
3. Copy the URL for the repository:

CleanShot-2024-03-09-at-11.48.38

1. Open Terminal
2. Change the current working directory to the location where you want the cloned directory.
3. Typegit clone, and then paste the URL you copied earlier:

Question 16

Steps to Create a new branch

Answer 16

1. On GitHub.com, navigate to the main page of the repository.
2. From the file tree view on the left, select the branch dropdown menu, then click View all branches.
3. Click New branch:
4. Under “Branch name”, type a name for the branch.
5. Under “Branch source”, choose a source for your branch.
6. Select the branch dropdown menu and click a branch.
7. Click Create branch:

Question 17

Explain how to add files to a repository

Answer 17

1. On GitHub.com, navigate to the main page of the repository.
2. Above the list of files, select the Add file dropdown menu and click Upload files. You can also drag and drop files into your browser:
3. In the “Commit message” field, type a short, meaningful commit message that describes the change you made to the file. If there are multiple authors, you can attribute the commit them here.
4. Below the commit message fields, decide whether to add your commit to the current branch or to a new branch (best practice is to NOT commit to main, but rather do a PR and merge).
5. Click Propose changes:

Question 18

How many MB’s of files can you upload to a repo via browser and how many via cli.

Answer 18

You can add up to 25 MB files to a repository via a browser. You can add up to 100 MB (each) files via the CLI. You can’t add/upload files to protected branches.

Question 19

how to view repository insights

Answer 19

Via the insights tab.

Question 20

What are the stats that you can view from repo insights?

Answer 20

• Pulse - Recent activity (PRs, issues, and so on).
• Contributors - who’s contributing and their stats.
• Community Standards - Checks for contributing guidelines files that repository maintainers can set to help collaborators make useful contributions to a project.
• Commits - Graph of commits over time.
• Code frequency - Additions/deletions over the history of the repo.
• Dependency Graph - A list of dependencies and dependents of the repo.
• Network - Timeline of the most recent commits to this repository and its network ordered by most recently pushed to.
• Forks - List of forks of the repo.

Question 21

Explain feature previews

Answer 21

You can see a list of features that are available in beta and a brief description for each feature. Each feature includes a link to give feedback.

1. In the upper-right corner, click your profile photo, then click Feature preview:
   2.To view details for a feature, in the left sidebar, click the feature’s name (where you can also enable/disble that feature):