GitHub Foundations - (GH-900) Exam Questions

Internal repositories on GitHub are accessible to all members within an enterprise. This facilitates collaboration and sharing of code and projects among all authorized members of the organization.

Example:
If John's enterprise creates an internal repository for sharing common libraries or tools, all enterprise members can access and contribute to the repository, fostering collaboration and efficiency.

Click here to know more about Repository visibility

Lois should edit his existing comment to include "@Peter" to ensure that Peter receives a notification about the discussion. Editing a comment to mention someone triggers a notification for the mentioned person, allowing them to join the conversation even if they were not initially included.

Click here to know more about it

In Git repositories, settings from .gitignore files are inherited from parent directories to child directories, meaning that settings defined in parent directories are applicable to child directories unless overridden by a .gitignore file in the child directory.

Click here to know more about Git ignoring files

GitHub maintains the visibility of topic names as public, regardless of whether they are created within private repositories. This means that even though the repository itself is private and inaccessible to others, the topics associated with it are visible to all GitHub users.

Click here to know more about adding Topics to a repository

A "commit" is a saved snapshot of the project's state at a specific point in time. Commits represent individual changes and serve as a way to track the history of the codebase.

In version control, a "commit" is like taking a snapshot of your project at a particular moment. It's like saving a checkpoint in a video game. Each commit contains a set of changes that you've made to the code. These changes could be adding new features, fixing bugs, or just making improvements.

Imagine you're working on a group project with others. When you finish a piece of work or make changes to the code that you want to keep track of, you "commit" those changes. This commit captures all the files you've modified and the specific changes you've made. It also includes a message where you can describe what you did.

Example:

Let's say you're building a website, and you just added a new page with some features. You make a commit to save these changes. Later, you might make another commit when you fix a typo on that page. Each commit is like a bookmark in your project's history, helping you and your team understand how the code evolved over time.

Commits are a fundamental aspect of version control, allowing developers to keep track of changes, collaborate effectively, and maintain a reliable history of the project.

Click here to know more about Git commit

Gists in GitHub serve as a simple and quick way to share bits of code with others. Think of gists as snippets or small pieces of code that you want to share, whether it's a handy function, a specific algorithm, or just a few lines of code that others may find useful.

Example:

Suppose you've written a small script to automate a common task or solve a particular problem. You can create a gist for that script, share the link with your colleagues, and they can easily view, fork, or even contribute to it.

When you share a gist, it can be either public or secret. Public gists are visible to anyone and can be searched by others, while secret gists aren't searchable but can be accessed if someone has the URL. It's like a quick way to showcase and collaborate on code without the need for a full-blown repository.

NOTE: Secret gists are are not private.

Click here to know more about Gist

To make your project easier to find and engage with, you can add relevant topics that describe what your project is about. These topics act like labels, helping others who are interested in similar things discover your project more easily.

Think of it like adding tags to your project. When someone searches for those tags, your project will show up in the results. It's like putting your project on the map for others to find!

Also, consider adding a README file. This is like a welcome sign for your project. It tells visitors what your project does, why it's useful, and how they can get started using it. It's a great way to introduce your project to the world!

NOTE: Topic names are always public, even if you create the topic from within a private repository.

NOTE: This question is important for the exam, and you may see a similar question on the exam.

Click here to know more about Topics

Click here to watch a video to know more about Topics

Click here to know more about Readmes

Pinning a discussion

You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.

NOTE: This question is important for the exam, and you may see a similar question on the exam.

Click here to know more about pinning a Discussion

GitHub Discussions is an open forum for conversation among maintainers and the community for a repository or organization on GitHub. All discussions must be created in a category. For repository discussions, people with maintain or admin permissions to the repository define the categories for discussions in that repository. For organization discussions, people with maintain or admin permissions to the source repository define the categories for discussions in that organization. Each category has a format: open-ended discussion, question and answer, or announcement.

When you enable discussions in a repository, the default categories available include Announcements, General, Ideas, Polls, Q&A, and Show and tell.

NOTE: This question is important for the exam, and you may see a similar question on the exam.

Click here to know more about Discussions Categories

With issue forms, you can optionally add:

• Assignees: People who will be automatically assigned to issues created with this template.

• Labels: Labels that will automatically be added to issues created with this template. If a label does not already exist in the repository, it will not be automatically added to the issue.

NOTE: This question is important for the exam, and you may see a similar question on the exam.

Click here to know more about it