The Codespaces lifecycle on GitHub includes several key steps:
Create: This is the step where a new Codespace is initiated.
Rebuild: A Codespace can be rebuilt to ensure that the environment is up-to-date with the latest code or configurations.
Delete: Once a Codespace is no longer needed, it can be deleted to free up resources.
Committing, cloning, or installing are typical Git operations but are not considered part of the specific lifecycle steps for a GitHub Codespace.

From a discussion post on GitHub, a user can Create an issue from the discussion. This feature allows users to turn a discussion into an actionable item by creating an issue directly from the discussion thread. This is particularly useful when a conversation identifies a bug, task, or enhancement that needs to be tracked in the repository.

In GitHub Discussions, several default categories are provided to help organize conversations within a project. One of the default categories is Show and tell. This category is designed for users to showcase their work, share progress, or discuss achievements with the community. The other options listed (Bug report, Daily check-in, Security concern) are not default categories but could be custom categories created by the repository maintainers.

As mentioned in the answer to Question no. 66, GitHub Actions workflows can reference actions from a variety of sources:
Any Public Repository:
Option A is correct. Actions can be sourced from any public GitHub repository.
The Same Repository as Your Workflow File:
Option B is correct. Actions within the same repository as the workflow file can be referenced directly.
A Published Docker Container Image on Docker Hub:
Option E is correct. Workflows can also use actions provided as Docker container images from Docker Hub.
Incorrect Options:
Option C and D are not relevant for directly referencing actions in workflows.
Reference:
GitHub Docs: Reusing Workflows

Saved replies in GitHub are a feature that allows users to create and save templates of commonly used responses for issues and pull requests. This feature can significantly enhance productivity and ensure consistent communication.
Saved Replies Are Tied to a User's Personal Account:
Option A is correct because saved replies are specific to a user's GitHub account, meaning they are accessible to the user across all repositories they have access to.
Saved Replies Allow Reusable Responses:
Option C is correct because the primary purpose of saved replies is to allow users to create reusable responses for issues and pull requests, saving time and ensuring consistency.
Incorrect Options:
Option B is incorrect because saved replies are not allocated at the enterprise level; they are specific to individual user accounts.
Option D is incorrect because saved replies do not send auto notifications; they are manually inserted by the user when responding to issues or pull requests.
Reference:
GitHub Docs: Using Saved Replies