On your team's page, you can use team discussions for conversations that span across projects or repositories and don't belong in a specific issue or pull request. Instead of opening an issue in a repository to discuss an idea, you can include the entire team by having a conversation in a team discussion.
Any organization member can post on your team's page or participate in a public discussion. Private posts are only visible to team members and organization owners, and public posts are visible to all members of the organization.
You can link to any team discussion to reference it elsewhere. You can pin important posts to your team's page for quick reference later. For more information, see "Pinning a team discussion."
Team discussions are available in organizations by default. Owners can disable team discussions for the entire organization. For more information, see "Disabling team discussions for your organization."
When someone posts or replies to a public discussion on a team's page, members of the team and members of any child teams receive email or web notifications. When someone posts or replies to a private discussion on a team's page, only members of the team receive notifications.
Tip: Depending on your notification settings, you'll receive updates by email, the web notifications page on GitHub Enterprise Cloud, or both. For more information, see "Configuring notifications."
By default, if your username is mentioned in a team discussion, you'll receive notifications for the post mentioning your username and any replies to that post. Also, by default, if you reply to a post, you will receive notifications for other replies to the post.
To turn off notifications for team discussions, you can unsubscribe to a specific discussion post or change your notification settings to unwatch or completely ignore a specific team's discussions. You can subscribe to notifications for a specific discussion post even if you're unwatching that team's discussions.
You can also use organization discussions to facilitate conversations across your organization. For more information, see "Enabling or disabling GitHub Discussions for an organization."