Foundations

Explain the different notification configuration options

*Not a clear answer here or I may have missed it in documentation* - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. - You gain access to a new repository or you've joined a new team. - There are new Dependabot alerts in your repository. - There are new deploy keys added to repositories that belong to organizations that you're an owner of

Describe the `base` and `compare` branches in a pull request

- **Base Branch:** The branch where changes will be merged (usually the main branch). - **Compare Branch:** The branch containing the changes to be merged into the base branch.

Explain basic Repository Navigation

- **Code:** Contains the project's files and folders. - **Issues:** Where project issues are tracked and discussed. - **Pull Requests:** Contains proposed changes and their discussion before they are merged. - **Actions:** Automation and CI/CD workflows. - **Projects:** Organizes and tracks tasks, issues, and notes. - **Wiki:** Collaborative documentation.

Explain the different options for providing a code review on a pull request (comment, approve, request changes, suggested changes)

- **Comment:** Add general comments or feedback. - **Approve:** Indicates that the changes are acceptable for merging. - **Request Changes:** Indicates that changes are needed before merging. - **Suggested Changes:** Offers specific suggestions directly in the code.

Describe the purpose of the pull request tabs (conversation, commits, checks, files changed)

- **Conversation:** Discussion and comments related to the PR. - **Commits:** List of commits included in the PR. - **Checks:** Status of automated tests and checks. - **Files Changed:** Visual representation of the changes made in the PR.

Describe the difference between discussions and issues

- **Discussions:** Provide a broader conversation platform encompassing various topics beyond the scope of code-related issues. - **Issues:** Specifically track bugs, enhancements, and tasks related to the codebase.

Explain the difference between GitHub Desktop and github.com

- **GitHub Desktop:** It's a desktop client providing a graphical interface to interact with Git repositories. It simplifies version control operations without using the command line. - **github.com:** Refers to the web-based interface of GitHub, where users can manage repositories, issues, pull requests, and collaborate on projects.

Identify the basic formatting syntax (headings, links, task lists, comments, etc.)

- **Headings:** Created using hash symbols (#). - **Links:** Enclosed in square brackets followed by the URL in parentheses. - **Task Lists:** Created using dashes and square brackets to create checkboxes. - **Comments:** Use `<!-- -->` for HTML-style comments.

Describe the difference between an issue, discussion, and pull request

- **Issue:** Tracks bugs, enhancements, tasks, or general discussion related to a repository. - **Discussion:** A broader conversation that can encompass various topics, ideas, or questions within a repository. - **Pull Request:** Proposes changes to a repository and is used for reviewing and merging code.

Describe the features in the user profile (metadata, achievements, profile readme, repositories, pinned repositories, stars, etc.)

- **Metadata:** Basic information about the user, such as name, bio, location, and social links. - **Achievements:** Badges or highlights for noteworthy contributions or achievements on GitHub. - **Profile Readme:** A customizable README displayed on the user's profile to showcase projects or personal information. - **Repositories:** Shows a list of repositories owned or contributed to by the user. - **Pinned Repositories:** Allows users to highlight specific repositories on their profile. - **Stars:** Indicates repositories the user has starred, signaling interest or approval.

Explain the different pull request statuses

- **Open:** PR is available for review and discussion. - **Closed:** PR is merged or closed without merging. - **Draft:** PR is in progress and not ready for review.

Recognize how to add and configure dev containers

- Access the Visual Studio Code Command Palette (Shift+Command+P / Ctrl+Shift+P), then start typing "add dev". Click Codespaces: Add Dev Container Configuration Files. - Click Create a new configuration. - Click Show All Definitions. - Click the definition you want to use. - Follow the prompts to customize your definition. - Click OK. - If you are working in a codespace, apply your changes by clicking Rebuild now in the pop-up at the bottom right of the window

Explain how to create a GitHub gist

- Click on the "Add gist" option on the user's GitHub profile or navigate to gist.github.com. - Enter the description, file name, code/content, and save the gist.

Describe how to create an issue

- Click on the "Issues" tab in the repository. - Click on the "New Issue" button. - Enter the issue title, description, and any necessary details. - Add labels, assignees, and milestones if needed. - Click "Submit new issue."

Explain how to create a new pull request

- Click on the "Pull requests" tab in the repository. - Click on "New pull request." - Choose the branches for comparison and review changes. - Add a title, description, and assignees. - Click "Create pull request."

Describe how to create, edit, and delete wiki pages

- Click on the "Wiki" tab in the repository and use the provided editor to create or edit pages. - Pages can be deleted by accessing the "Manage wiki" option.

Explain how to save a repository with stars

- Click the "Star" button on the top right of a repository to bookmark it. - Starring a repository allows easy access and indicates interest in the project.

Identify how to link activity within a pull request

- Comments within a PR can reference other issues, PRs, or discussions using the '#' symbol followed by the number or name.

Explain the relationship of commits on a pull request

- Commits associated with a PR represent changes proposed by the PR. - They showcase the history of changes made to the codebase in the context of the PR.

Describe draft pull requests

- Draft PRs indicate that work is in progress and not ready for review. - They allow contributors to open PRs to share progress without triggering automated workflows or reviews.

Explain feature previews

- Feature previews on GitHub give users early access to upcoming functionalities or changes before they're officially released. - Users can opt-in to test these features and provide feedback.

Identify how to view repository insights

- Insights tab in the repository provides statistics like traffic, contributors, and more. - Use graphs and charts to understand codebase trends, traffic sources, and contributors' activities

Explain the difference between issue templates and issue forms

- Issue Templates: Predefined structures guiding users to include specific information when creating an issue. - Issue Forms: can create issue templates that have customizable web form fields. You can encourage contributors to include specific, structured information by using issue forms in your repository. Issue forms are written in YAML using the GitHub form schema.

Identify how to assign issues

- Open an issue in the repository. - Click on "Assignees" and select the user(s) to assign the issue.

Explain basic issue management

- Regularly review and triage incoming issues. - Assign labels, milestones, and assignees to organize and prioritize issues. - Communicate and update the status of issues as work progresses.

Describe code review with a codeowners file

- The CODEOWNERS file specifies individuals or teams responsible for reviewing code in specific areas of the repository.

Recognize how to comment on a posted link to a line or lines of code from a file

- Use the "Lines" tab in a PR to leave comments on specific lines of code by clicking the '+' icon next to the line numbers.

Describe how to search and filter issues

- Use the search bar in the "Issues" tab of the repository to search by keywords, labels, assignees, or specific filters. - Advanced search options allow complex queries to find specific issues.

Describe how to link a PR to an issue

- When creating a PR, GitHub automatically suggests related issues in the PR description. - You can manually link a PR to an issue by mentioning the issue number in the PR description or comment using keywords like "closes," "fixes," or "resolves" followed by the issue number (e.g., "Closes #123").

Describe the different GitHub accounts (personal, organization, enterprise)

1. **Personal Account:** This is an individual's GitHub account used for personal projects, open-source contributions, and collaborations. It's free to use for public repositories. 2. **Organization Account:** Organizations on GitHub allow groups of people to collaborate across many projects at once. These accounts can manage team permissions, repositories, and have their own set of security and administrative features. 3. **Enterprise Account:** GitHub Enterprise is a self-hosted version of GitHub that can be deployed on-premises or on a cloud infrastructure. It's typically used by larger organizations that require additional control, security, and compliance features.

Describe a GitHub Repository

A GitHub repository, or repo, is a storage space where your project files, commit history, and branches are stored. It contains folders, files, images, and everything else needed for your project. Repositories on GitHub can be public or private and are accessible to collaborators and users with the appropriate permissions.

Describe a pull request

A PR is a proposed set of changes to a repository, allowing code review and discussion before merging into the main codebase.

Describe GitHub Codespaces

A codespace is a development environment that's hosted in the cloud. You can customize your project for GitHub Codespaces by committing configuration files to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project.

Describe a Commit

A commit in Git is a snapshot of changes made to files in a repository. It represents a specific point in the project's history and includes a unique identifier (hash), the author's information, a commit message describing the changes, and references to the changes made.

Define a remote in Git Terminology

A remote in Git refers to a version of a repository that is hosted on a server or another computer. It enables collaboration by allowing users to fetch, pull, and push changes between their local repository and the remote repository, facilitating team collaboration and sharing of code changes.

Describe the available features with GitHub Desktop

Add and clone repositories. Add changes to your commit interactively. Quickly add co-authors to your commit. Check out branches with pull requests and view CI statuses. Compare changed images.

Explain how to create a branch from an issue

Anyone with write permission to a repository can create a branch for an issue. You can link multiple branches for an issue. By default, the new branch is created in the current repository, and from the default branch. - On GitHub.com, navigate to the main page of the repository. - Under your repository name, click Issues. - In the list of issues, click the issue that you would like to create a branch for. - In the right sidebar under "Development", click Create a branch. If the issue already has a linked branch or pull request, select the cogwheel and click Create a branch. - Optionally, in the "Branch name" field, type a branch name. - Optionally, select the Repository destination dropdown menu, then choose a repository. - Under "What's next", select whether you want to work on the branch locally or to open the branch in GitHub Desktop. - Click Create branch.

Recognize how to add assignees to issues and pull requests

Assignees can be added to issues or PRs by editing the issue/PR and selecting assignees from the dropdown.

Describe Branching

Branching in Git allows for creating separate lines of development, diverging from the main codebase. It enables developers to work on new features, bug fixes, or experiments without altering the main codebase. Branches can be merged back into the main branch (often called 'master' or 'main') when changes are ready.

Explain the difference between projects and projects classic

Classic Projects are made up of issues, poll requests, and notes that are similar to the way boards work in the New Experience. With classic Projects you can add a project at a repo level, but with New Projects, your projects are created at the organizational level, and can be attached to any of your repos

Identify how do to start a GitHub codespace

Click on the "Code" button in a repository and select "Open with Codespaces."

Explain how to subscribe to notification threads

Click the "Subscribe" button in the notification thread or issue/PR to receive notifications for updates.

Describe the codespace lifecycle

Creating a Codespace Rebuilding a Codespace Stopping a Codespace Deleting a Codespace

Identify how to mark a comment as an answer to a discussion

Discussion authors and users with the triage role or greater for a repository can mark a comment as the answer to a discussion in the repository. Similarly, discussion authors and users with the triage role or greater for the source repository for organization discussions can mark a comment as the answer to a discussion in the organization. - On GitHub.com, navigate to the main page of the repository or organization. - Under your repository or organization name, click Discussions. - In the list of discussions, click the unanswered discussion you want to mark as answered. - In the discussion, find the comment you want to mark as the answer. - Below the comment, click Mark as answer.

Explain where you can find existing GitHub Actions

Explore and discover existing GitHub Actions through the GitHub Marketplace or by browsing public repositories.

Identify the notification filtering options

Filter notifications by repository, organization, or type of event (issues, PRs, comments, etc.).

Describe how to fork and clone a gist

Gists can be forked directly from the gist page by clicking the fork button next to the star button in the top right corner. To clone a gist, select the Embed dropdown menu, then click Clone via HTTPS or Clone via SSH.

Explain the difference between Git and GitHub

Git is the version control system that manages and tracks changes in source code, while GitHub is a web-based platform that uses Git for version control and provides additional features like hosting repositories, collaboration tools, and project management.

Explain where you can use GitHub Actions within GitHub (general event types)

GitHub Actions can be triggered by various events like push, pull request, issue creation, etc.

Describe GitHub Actions (basic understanding)

GitHub Actions is a continuous integration and continuous delivery (CI/CD) platform that allows you to automate your build, test, and deployment pipeline.

Describe the difference between GitHub Copilot for Individuals and GitHub Copilot for Business

GitHub Copilot for Individuals is intended for personal use, whereas GitHub Copilot for Business might include additional features tailored for organizations and teams. With Copilot Business, you can manage access to GitHub Copilot for organizations. Once you grant an organization access to GitHub Copilot, the administrators of that organization can grant access to individuals and teams.

Describe GitHub Copilot

GitHub Copilot is an AI-powered code completion tool that helps developers write code.

Describe the different deployment options for GitHub Enterprise

GitHub Enterprise includes two deployment options: GitHub Enterprise Cloud, which is cloud-hosted and part of GitHub.com, and GitHub Enterprise Server, which is self-hosted

Describe the GitHub Flow

GitHub Flow is a lightweight, branch-based workflow that uses branches for feature development and pull requests for code review and merging. It typically involves creating a branch for each new feature, making changes, opening a pull request to discuss and review the changes, and merging the branch back into the main branch once the changes are approved.

Describe GitHub's products for organization accounts (free for organizations, teams)

GitHub Free for organizations - With GitHub Free for organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set or unlimited private repositories with a limited feature set. - In addition to the features available with GitHub Free for personal accounts, GitHub Free for organizations includes: - Team access controls for managing groups GitHub Team is the version of GitHub Pro for organizations. GitHub Team is better than GitHub Free for organizations because it provides increased GitHub Actions minutes and extra GitHub Packages storage. Let's go over the extra features in GitHub Team that help with team collaboration: - GitHub Support via email - 3,000 GitHub Actions minutes per month - 2 GB GitHub Packages storage - Advanced tools and insights in private repositories: - Required pull request reviewers - Multiple pull request reviewers - Draft pull requests - Team pull request reviewers - Protected branches - Code owners - Scheduled reminders - GitHub Pages - Wikis - Repository insight graphs for pulse, contributors, traffic, commits, code frequency, network, and forks - The option to enable or disable GitHub Codespaces

Describe GitHub Pages

GitHub Pages allows users to host static websites directly from their GitHub repositories.

Describe GitHub Projects

GitHub Projects organize tasks, issues, and pull requests into boards with columns for tracking progress.

Identify the text formatting toolbar on issue and pull request comments

GitHub uses Markdown for formatting text in comments. It offers a toolbar with options like bold, italic, code formatting, lists, links, and more for easy text formatting.

Explain how to manage notifications through the GitHub Mobile app

In the GitHub Mobile app, users can manage notifications by accessing the notification center, where they can mark notifications as read, subscribe or unsubscribe to threads, and manage notification settings.

Describe how to manage notification subscriptions

In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click Notification settings. On the notifications settings page, choose how you receive notifications when: There are updates in repositories or team discussions you're watching or in a conversation you're participating in.

Describe project insights

Insights in a project offer analytics and visual representations of progress, timelines, and completion rates.

Explain the use of labels

Labels categorize and prioritize items in a project

Describe the available features with GitHub Mobile

Manage, triage, and clear notifications from github.com. Read, review, and collaborate on issues and pull requests. Edit files in pull requests. Search for, browse, and interact with users, repositories, and organizations. Receive a push notification when someone mentions your username. Schedule push notifications for specific custom hours. Secure your GitHub.com account with two-factor authentication. Verify your sign in attempts on unrecognized devices.

Describe Markdown

Markdown is a lightweight markup language used to format plain text. It allows users to add formatting elements like headings, lists, links, code blocks, and more to plain text documents.

Explain how to create a new repository

On GitHub, click the "+" on the top right and select "New Repository." - Provide a name, description, visibility, and other settings. - Initialize with a README if needed. - Click "Create Repository."

Describe how to clone a repository

On GitHub, navigate to the repository. - Click "Code" and copy the repository URL. - On the local machine, open Git Bash or terminal. - Use the `git clone <repository_URL>` command to clone the repository.

Explain how to add files to a repository

On GitHub.com, navigate to the main page of the repository. Above the list of files, select the Add file dropdown menu and click Upload files. Alternatively, you can drag and drop files into your browser. To select the files you want to upload, drag and drop the file or folder, or click choose your files. In the "Commit message" field, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is the default branch, you should choose to create a new branch for your commit and then create a pull request. Click Propose changes

Describe how to create a new branch

On GitHub.com, navigate to the main page of the repository. - From the file tree view on the left, select the branch dropdown menu, then click View all branches. You can also find the branch dropdown menu at the top of the integrated file editor. - Click New Branch - Under "Branch name", type a name for the branch. - Under "Branch source", choose a source for your branch. - If your repository is a fork, select the repository dropdown menu and click your fork or the upstream repository. - Select the branch dropdown menu and click a branch. - Click Create branch

Explain the layout options for projects

Projects can be organized as boards, lists, or tables to track progress in different styles.

Recognize repository permission levels

Read - Recommended for non-code contributors who want to view or discuss your project. This level is good for anyone that needs to view the content within the repository but doesn't need to actually make contributions or changes. Triage - Recommended for contributors who need to proactively manage issues and pull requests without write access. This level could be good for some project managers who manage tracking issues but don't make any changes. Write - Recommended for contributors who actively push to your project. Write is the standard permission for most developers. Maintain - Recommended for project managers who need to manage the repository without access to sensitive or destructive actions. Admin - Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository. These people are repository owners and administrators.

Describe the different features to maintaining a repository

Regularly updating and managing issues, pull requests, and documentation. - Ensuring a clean and understandable codebase. - Reviewing and merging contributions from collaborators.

Describe the benefits of using a saved reply

Saves time and maintains consistency by reusing common responses to comments or issues.

Describe the different customizations you can personalize with GitHub Codespaces

Settings Sync: You can synchronize your Visual Studio Code (VS Code) settings between the desktop application and the VS Code web client. Dotfiles: You can use a dotfiles repository to specify scripts, shell preferences, and other configurations. Rename a Codespace: When you create a Codespace, it's assigned an autogenerated display name. If you have multiple Codespaces, the display name helps you to differentiate between Codespaces. You can change the display name for your Codespace. Change your shell: You can change your shell in a Codespace to keep the setup you're used to. When you're working in a Codespace, you can open a new terminal window with a shell of your choice, change your default shell for new terminal windows, or install a new shell. You can also use dotfiles to configure your shell. Change the machine type: You can change the type of machine that's running your Codespace, so that you're using resources appropriate for the work you're doing. Set the default editor: You can set your default editor for Codespaces in your personal settings page. Set your editor preference so that when you create a Codespace or open an existing Codespace, it opens to your default editor. Set the default region: You can set your default region in the GitHub Codespaces profile settings page to personalize where your data is held. Set the timeout: A Codespace will stop running after a period of inactivity. By default this period is 30 minutes, but you can specify a longer or shorter default timeout period in your personal settings on GitHub. Configure automatic deletion: Inactive Codespaces are automatically deleted. You can choose how long your stopped Codespaces are retained, up to a maximum of 30 days.

Explain the options available with discussions (announcements, ideas, polls, Q&A, show and tell)

Share announcements and information, gather feedback, plan, and make decisions Ask questions, discuss and answer the questions, and mark the discussions as answered Create polls to gauge community opinion Upvote discussions and comments to give higher visibility to ideas you find valuable Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows

Explain where to find and use slash commands

Slash commands in GitHub are special shortcuts typed into comments or descriptions, prefixed with a "/", enabling users to perform actions like assigning tasks, labeling issues, and more.

Describe repository templates

Templates allow creating a new repository based on a predefined structure. - Users can create custom templates for issues, pull requests, or the repository itself to standardize workflows.

Explain how to use keywords in issues

To show that a fix is in progress and to automatically close the issue when someone merges the pull request, type one of the following keywords followed by a reference to the issue. For example, Closes #10 or Fixes octo-org/octo-repo#100. Examples: - close - closes - closed - fix - fixes - fixed - resolve - resolves - resolved Keywords like "closes," "fixes," or "resolves" followed by the issue number automatically close the issue once the associated PR is merged.

Explain how to get started using GitHub Copilot

To use GitHub Copilot you must have an active GitHub Copilot subscription. You can start using GitHub Copilot by installing the extension in your preferred environment.

Explain how to secure your account with 2FA

Two-Factor Authentication (2FA) adds an extra layer of security to GitHub accounts by requiring a second verification step during login.

Describe how to find threads where you are at-mentioned

Use the "Mentions" tab in the notification center to find threads where you've been mentioned.

Describe the configuration options for projects

Users can set up automation, assignees, and labels for managing tasks within a project.

Explain how to create, edit, and delete saved replies

When commenting on an issue or pull request, you can add a saved reply that you've already set up. The saved reply can be the entire comment or if you want to customize it, you can add or delete content. Create - In the upper-right corner of any page, click your profile photo, then click Settings. - In the "Code, planning, and automation" section of the sidebar, click Saved replies. - Under "Add a saved reply", add a title for your saved reply. - In the "Write" field, add the content you'd like to use for the saved reply. - To review your reply, click Preview. - Click Add saved reply. Edit - In the upper-right corner of any page, click your profile photo, then click Settings. - In the "Code, planning, and automation" section of the sidebar, click Saved replies. - Under "Saved replies," next to the saved reply you want to edit, click the pencil icon. - Under "Edit saved reply," edit the title or content of the saved reply. - Click Update saved reply. Delete - In the upper-right corner of any page, click your profile photo, then click Settings. - In the "Code, planning, and automation" section of the sidebar, click Saved replies. - Under "Saved replies", next to the saved reply you want to delete, click x .

Explain how to convert a discussion to an issue

When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository, or source repository for organization discussions, can bulk convert issues based on labels. - On GitHub.com, navigate to the main page of the repository or organization. - Under your repository name, click Issues. - In the list of issues, click the issue you'd like to convert. - In the right margin of an issue, click Convert to discussion. - Select the Choose a category drop-down menu, and click a category for your discussion. - Click I understand, convert this issue to a discussion.

Explain the visibility of wiki pages

Wiki pages can be public or private, depending on the repository's visibility settings.

Explain GitHub Wiki pages

Wiki pages in a repository are collaborative documentation pages where users can add and edit content.

Explain EMUs (Enterprise Managed Users)

With Enterprise Managed Users, you manage the lifecycle and authentication of your users on GitHub.com from an external identity management system, or IdP. You can provide access to GitHub Enterprise Cloud to people who have existing identities and group membership on your IdP. Your IdP provisions new user accounts with access to your enterprise on GitHub.com. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP.

Describe GitHub's products for personal accounts (free, pro)

With GitHub Free, a personal account includes: - GitHub Community Support - Dependabot alerts - Two-factor authentication enforcement - 500 MB GitHub Packages storage - 120 GitHub Codespaces core hours per month - 15 GB GitHub Codespaces storage per month - GitHub Actions: - 2,000 minutes per month - Deployment protection rules for public repositories GitHub Pro accounts include all of the features of a GitHub Free account, plus the following advanced features: - GitHub Support via email - 3,000 GitHub Actions minutes per month - 2 GB GitHub Packages storage - 180 GitHub Codespaces core hours per month - 20 GB GitHub Codespaces storage per month - Advanced tools and insights in private repositories: - Required pull request reviewers - Multiple pull request reviewers - Protected branches - Code owners - Autolinked references - GitHub Pages - Wikis - Repository insight graphs for pulse, contributors, traffic, commits, code frequency, network, and forks

Explain how to use project workflows

Workflows automate processes within projects, triggering actions based on predefined events.

Describe how to use and create template repos

You can make an existing repository a template, so you and others can generate new repositories with the same directory structure, branches, and files. - On GitHub.com, navigate to the main page of the repository. - Under your repository name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings. - Select Template repository.

Explain how to use the github.dev editor

You can open any GitHub repository in github.dev in either of the following ways: - To open the repository in the same browser tab, press "." while browsing any repository or pull request on GitHub. - To open the repository in a new browser tab, press ">". - Change the URL from "github.com" to "github.dev". - When viewing a file, select the dropdown menu and click github.dev.

Recognize how to pin 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. Pinning a discussion globally You can pin up to four important discussions above the list of discussions for the repository or organization. - On GitHub.com, navigate to the main page of the repository or organization. - Under your repository or organization name, click Discussions. - In the list of discussions, click the discussion you want to view. - In the right sidebar, click Pin discussion. - Optionally, customize the look of the pinned discussion. - Click Pin discussion. Pinning a discussion to a category You can pin up to four important discussions above the list of discussions in a specific category. - On GitHub.com, navigate to the main page of the repository or organization. - Under your repository or organization name, click Discussions. - In the list of discussions, click the discussion you want to view. - In the right sidebar, click Pin discussion to CATEGORY. - To confirm, click Pin to CATEGORY.

Describe how to pin an issue

You can pin up to three important issues above the issues list in your repository. Who can use this feature People with write access to a repository can pin issue in the repository. - On GitHub.com, navigate to the main page of the repository. - Under your repository name, click Issues. - In the list of issues, click the issue you'd like to pin. - In the right sidebar, click Pin issue.

Identify how to share a deep link to a GitHub codespace

You can use these URLs to link to the codespace creation page for your repository. Replace the text in uppercase letters. Create a codespace for the default branch of the repository: https://codespaces.new/OWNER/REPO-NAME Create a codespace for a specific branch of the repository: https://codespaces.new/OWNER/REPO-NAME/tree/BRANCH-NAME Create a codespace for the topic branch of a pull request: https://codespaces.new/OWNER/REPO-NAME/pull/PR-SHA

Describe Git

a distributed version control system designed for tracking changes in source code during software development. It allows multiple developers to collaborate on projects, maintain versions, track changes, and merge code contributions into a cohesive whole. Git provides powerful branching and merging capabilities.

Describe Version Control

a system that records changes to a file or a set of files over time so that you can recall specific versions later. It helps in tracking modifications, reverting to previous stages, comparing changes over time, and collaborating with others on a project.

Define Distributed Version Control

a type of version control system where the entire repository, including its full history and all branches, is mirrored on every user's computer. This allows for collaboration without the need for a central server and enables users to work offline.

Describe GitHub

a web-based platform built around Git that provides hosting for software development and version control using Git. It offers various collaboration features like bug tracking, feature requests, task management, and wikis for every project. GitHub allows users to host their Git repositories online and facilitates collaboration among teams.

Explain the differences between the github.dev editor and a GitHub Codespace

github.dev offers lightweight editing directly in the browser, while Codespaces provide a fully-featured development environment.

Explain the use of milestones

milestones group items based on completion goals.

Describe the components of a good README and the recommended repository files (LICENSE, CONTRIBUTING, CODEOWNERS)

**README:** Describes the project, its purpose, installation instructions, usage, and any other pertinent information. - **LICENSE:** Contains the licensing information for the project. - **CONTRIBUTING:** Guidelines for contributors regarding how to contribute to the project. - **CODEOWNERS:** Specifies individuals or teams responsible for code maintenance in specific areas of the repository.