Manually linking a pull request or branch to an issue using the issue sidebar Anyone with write permissions to a repository can manually link a pull request or branch to an issue from the issue sidebar.
You can manually link up to ten issues to each pull request. The issue can be in a different repository than the linked pull request or branch. Your last selected repository will be remembered.
1. On GitHub, navigate to the main page of the repository.
2. Under your repository name, click Issues.

3. In the list of issues, click the issue that you'd like to link a pull request or branch to.
*-> 4. In the right sidebar, click Development.

5. Click the repository containing the pull request or branch you want to link to the issue.
6. Click the pull request or branch you want to link to the issue.
7. Click Apply.
Reference:
https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull- request-to-an-issue

Discussions Polls
Polls are available on GitHub Discussions! Polls make it easy for community members to gauge interest, vote, and interact with one another without having to comment.

[B] You can reflect your group or company's hierarchy within your GitHub organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams.
[C] Team visibility
Teams can be visible or secret:
Visible teams can be viewed and @mentioned by every organization member.
Secret teams are only visible to the people on the team and people with owner permissions.
They're great for hiding teams with sensitive names or members, such as those used for working with external partners or clients. Secret teams cannot be nested under parent teams or have child teams.
Reference:
https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams

GitHub Projects offers different layout options to help teams organize and visualize their work, including Table, Board, and Timeline. The Table view presents structured data like a spreadsheet, the Board layout uses a Kanban-style interface for task management, and the Timeline layout helps track progress over time.
Option A is CORRECT because GitHub Projects supports three main layout options:
Table (a high-density spreadsheet-style layout)
Board (a Kanban-style task board)
Timeline (a roadmap-style view useful for planning over time)
References:
https://docs.github.com/en/issues/planning-and-tracking-with-projects/customizing-views-in-your- project/changing-the-layout-of-a-view
https://github.blog/developer-skills/github/getting-started-with-project-planning-on-github/

The feature you can use to merge proposed changes in a repository on GitHub is Pull requests.
Pull requests are a core feature of GitHub, allowing developers to propose changes to a codebase, review code, discuss the changes, and eventually merge them into the main branch.
This collaborative workflow ensures that code is reviewed and vetted before becoming part of the project.