jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Hack week 2025: remove unneeded FBV instances (9) - Discussions (#53946)

Browse Source
This commit is contained in:
mc
2025-01-16 11:10:55 +00:00
committed by GitHub
parent 648bb382c6
commit ba096812c3
31 changed files with 89 additions and 110 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
content/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs.md
View File

@@ -16,7 +16,7 @@ versions:
## About re-running workflows and jobs
Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. The workflow will use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see [AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy).{% endif %}{% ifversion debug-reruns %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging).{% endif %}
Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. The workflow will use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see [AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy).{% endif %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging).
## Re-running all the jobs in a workflow
@@ -46,15 +46,12 @@ To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id
gh run rerun RUN_ID
```
{% ifversion debug-reruns %}
{% data reusables.actions.enable-debug-logging-cli %}
```shell
gh run rerun RUN_ID --debug
```
{% endif %}
To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
```shell
@@ -88,14 +85,12 @@ To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the
gh run rerun RUN_ID --failed
```
{% ifversion debug-reruns %}
{% data reusables.actions.enable-debug-logging-cli %}
```shell
gh run rerun RUN_ID --failed --debug
```
{% endif %}
{% endcli %}
## Re-running a specific job in a workflow
@@ -122,14 +117,12 @@ To re-run a specific job in a workflow run, use the `run rerun` subcommand with
gh run rerun --job JOB_ID
```
{% ifversion debug-reruns %}
{% data reusables.actions.enable-debug-logging-cli %}
```shell
gh run rerun --job JOB_ID --debug
```
{% endif %}
{% endcli %}
{% endif %}

4
content/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/enabling-debug-logging.md
View File

@@ -21,12 +21,8 @@ These extra logs are enabled by setting secrets or variables in the repository c
For more information on setting secrets and variables, see [AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions) and [AUTOTITLE](/actions/learn-github-actions/variables).
{% ifversion debug-reruns %}
Additionally, anyone who has access to run a workflow can enable runner diagnostic logging and step debug logging for a workflow re-run. For more information, see [AUTOTITLE](/actions/managing-workflow-runs/re-running-workflows-and-jobs).
{% endif %}
## Enabling runner diagnostic logging
Runner diagnostic logging provides additional log files that contain information about how a runner is executing a job. Two extra log files are added to the log archive:

5
content/authentication/keeping-your-account-and-data-secure/viewing-and-managing-your-sessions.md
View File

@@ -2,7 +2,10 @@
title: Viewing and managing your sessions
intro: You can view and revoke your active sessions in your settings.
versions:
feature: device-and-settings-management-page
fpt: '*'
ghec: '*'
ghes: '*'
type: how_to
topics:
- SSO

11
content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
View File

@@ -2,7 +2,9 @@
title: About discussions
intro: 'Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}.'
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
---
@@ -20,7 +22,7 @@ With {% data variables.product.prodname_discussions %}, the community for your p
You might use repository discussions to discuss topics that are specific to the repository. If your project spans multiple repositories, you might use organization discussions to discuss topics that aren't specific to a single repository in your organization.
{% ifversion discussions-closable %}{% data reusables.discussions.closing-discussions %} For more information, see [Closing a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#closing-a-discussion).{% else %}You don't need to close a discussion like you close an issue or a pull request.{% endif %}
{% data reusables.discussions.closing-discussions %} For more information, see [Closing a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#closing-a-discussion).
If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who has access to the repository can create and participate in discussions for the repository. If an organization owner enables {% data variables.product.prodname_discussions %} for an organization, anyone who can view the source repository can create an organization discussion.
@@ -40,7 +42,7 @@ For more information on creating polls, see [AUTOTITLE](/discussions/collaborati
## About discussion organization
You can organize discussions with categories{% ifversion discussions-category-section %}, sections, {% endif %} and labels.
You can organize discussions with categories, sections, and labels.
{% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %}
@@ -48,8 +50,7 @@ For discussions with a question/answer format, an individual comment within the
{% data reusables.discussions.about-announcement-format %}
{% ifversion discussions-category-section %}
{% data reusables.discussions.category-sections %}{% endif %}
{% data reusables.discussions.category-sections %}
For more information, see [AUTOTITLE](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions).

4
content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
View File

@@ -4,7 +4,9 @@ shortTitle: Collaborating with maintainers
intro: 'You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion.'
permissions: 'People with read access to a repository can start and participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can start and participate in discussions and polls in the organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
---

5
content/discussions/collaborating-with-your-community-using-discussions/index.md
View File

@@ -3,10 +3,11 @@ title: Collaborating with your community using discussions
shortTitle: Collaborating using discussions
intro: Gather and discuss your project with community members and other maintainers.
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
children:
- /about-discussions
- /participating-in-a-discussion
- /collaborating-with-maintainers-using-discussions
---

4
content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
View File

@@ -3,7 +3,9 @@ title: Participating in a discussion
intro: 'You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}.'
permissions: 'People with read access to a repository can participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can participate in discussions and polls in that organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
shortTitle: Participate in discussion
---

4
content/discussions/guides/best-practices-for-community-conversations-on-github.md
View File

@@ -3,7 +3,9 @@ title: Best practices for community conversations on GitHub
shortTitle: Best practices for community conversations
intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to an issue when you are ready to scope out the work.'
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
---

4
content/discussions/guides/finding-your-discussions.md
View File

@@ -2,7 +2,9 @@
title: Finding your discussions
intro: You can easily access every discussion you've created or participated in.
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
shortTitle: Find discussions
redirect_from:
- /discussions/guides/finding-discussions-across-multiple-repositories

4
content/discussions/guides/granting-higher-permissions-to-top-contributors.md
View File

@@ -2,7 +2,9 @@
title: Granting higher permissions to top contributors
intro: Repository administrators can promote any community member to a moderator and maintainer.
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
shortTitle: Grant higher permissions
---

5
content/discussions/guides/index.md
View File

@@ -3,10 +3,11 @@ title: Discussions guides
shortTitle: Guides
intro: Discover pathways to get started or learn best practices for participating or monitoring your community's discussions.
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
children:
- /best-practices-for-community-conversations-on-github
- /finding-your-discussions
- /granting-higher-permissions-to-top-contributors
---

4
content/discussions/index.md
View File

@@ -32,7 +32,9 @@ changelog:
examples_source: data/product-examples/discussions/community-examples.yml
layout: product-landing
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
communityRedirect:
name: Provide GitHub Feedback
href: 'https://github.com/orgs/community/discussions/categories/discussions'

4
content/discussions/managing-discussions-for-your-community/creating-discussion-category-forms.md
View File

@@ -3,7 +3,9 @@ title: Creating discussion category forms
shortTitle: Create discussion category forms
intro: You can customize the templates that are available for community members to use when they open new discussions in your repository.
versions:
feature: discussion-category-forms
fpt: '*'
ghes: '*'
ghec: '*'
---
## About discussion category forms

5
content/discussions/managing-discussions-for-your-community/index.md
View File

@@ -3,7 +3,9 @@ title: Managing discussions for your community
shortTitle: Managing discussions
intro: 'You can enable and configure {% data variables.product.prodname_discussions %} for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.'
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
children:
- /managing-discussions
- /managing-categories-for-discussions
@@ -12,4 +14,3 @@ children:
- /creating-discussion-category-forms
- /syntax-for-discussion-category-forms
---

24
content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
View File

@@ -3,7 +3,9 @@ title: Managing categories for discussions
intro: 'You can categorize discussions to organize conversations for your community members, and you can choose a format for each category.'
permissions: Repository administrators and people with write or greater access to a repository can manage categories for discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage categories for discussions in the organization.
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
shortTitle: Manage categories
redirect_from:
- /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository
@@ -18,8 +20,7 @@ redirect_from:
Each category must have a unique name and emoji pairing, and can be accompanied by a detailed description stating its purpose. Categories help maintainers organize how conversations are filed and are customizable to help distinguish categories that are Q&A or more open-ended conversations. {% data reusables.discussions.repository-category-limit %} For more information, see [AUTOTITLE](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions).
{% ifversion discussions-category-section %}
{% data reusables.discussions.category-sections %}{% endif %}
{% data reusables.discussions.category-sections %}
## Default categories
@@ -42,12 +43,9 @@ Each category must have a unique name and emoji pairing, and can be accompanied
![Screenshot of the "Manage discussion categories" page. A button, labeled "New category", is highlighted with an orange outline.](/assets/images/help/discussions/click-new-category-button.png)
1. {% data reusables.discussions.edit-category-details %}
{% ifversion discussions-category-section %}
{% data reusables.discussions.add-category-to-section %}{% endif %}
{% data reusables.discussions.add-category-to-section %}
1. Click **Create**.
{% ifversion discussions-category-section %}
## Creating a section
1. Navigate to the main page of the repository or organization where you want to create a category.
@@ -58,7 +56,6 @@ Each category must have a unique name and emoji pairing, and can be accompanied
1. Edit the emoji and title of the section.
1. Select the categories that you want to add to the section. A category can only belong to one section at a time.
1. Click **Create**.
{% endif %}
## Editing a category
@@ -69,12 +66,9 @@ You can edit a category to change the category's emoji, title, description, and
{% data reusables.discussions.edit-categories %}
1. To the right of a category in the list, click {% octicon "pencil" aria-label="The pencil icon" %}.
1. {% data reusables.discussions.edit-category-details %}
{% ifversion discussions-category-section %}
{% data reusables.discussions.add-category-to-section %}{% endif %}
{% data reusables.discussions.add-category-to-section %}
1. Click **Save changes**.
{% ifversion discussions-category-section %}
## Editing a section
You can edit a section to change the section's emoji and title, and to add and remove categories from the section.
@@ -85,13 +79,12 @@ You can edit a section to change the section's emoji and title, and to add and r
1. To the right of a section in the list, click {% octicon "pencil" aria-label="The pencil icon" %}.
1. Edit the section's emoji and title, and select or deselect the categories that you want to add or remove from the section.
1. Click **Update**.
{% endif %}
## Deleting a category
When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose.
{% ifversion discussions-category-section %}When you delete a section, all categories within the section will no longer belong to a section.{% endif %}
When you delete a section, all categories within the section will no longer belong to a section.
1. Navigate to the main page of the repository or organization where you want to delete a category.
{% data reusables.discussions.discussions-tab %}
@@ -99,8 +92,6 @@ When you delete a category, {% data variables.product.product_name %} will move
1. Select the dropdown menu, and click a new category for any discussions in the category you're deleting.
1. Click **Delete & Move**.
{% ifversion discussions-category-section %}
## Deleting a section
When you delete a section, all categories within the section will no longer belong to a section.
@@ -109,4 +100,3 @@ When you delete a section, all categories within the section will no longer belo
{% data reusables.discussions.discussions-tab %}
1. To the right of a section in the list, click {% octicon "trash" aria-label="The trash icon" %}.
1. In the dialog box, review the information about deleting a section, then click **Delete**.
{% endif %}

41
content/discussions/managing-discussions-for-your-community/managing-discussions.md
View File

@@ -3,7 +3,9 @@ title: Managing discussions
intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
permissions: Repository administrators and people with {% ifversion discussions-moderators-control-who-can-report %}triage{% else %}write{% endif %} or greater access to a repository can manage discussions in the repository. Repository administrators and people with {% ifversion discussions-moderators-control-who-can-report %}triage{% else %}write{% endif %} or greater access to the source repository for organization discussions can manage discussions in the organization.
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
shortTitle: Manage discussions
redirect_from:
- /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
@@ -20,7 +22,7 @@ As a discussions maintainer, you can create community resources to encourage dis
When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion).
You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see [AUTOTITLE](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion).
You can pin a discussion to the top of the list of discussions for the repository or organization. You can also pin a discussion to a specific category. For more information, see [AUTOTITLE](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion).
For more information on facilitating a healthy discussion, see [AUTOTITLE](/communities/moderating-comments-and-conversations).
@@ -46,7 +48,6 @@ You can also move a discussion to a different category. It's not possible to mov
## Pinning a discussion
{% ifversion discussions-category-specific-pins %}
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.
This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
@@ -55,25 +56,18 @@ This is what it looks like when you have a globally pinned discussion and a disc
### Pinning a discussion globally
{% endif %}
You can pin up to four important discussions above the list of discussions for the repository or organization.
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
1. In the right sidebar, click **{% octicon "pin" aria-hidden="true" %} Pin discussion**.
{% ifversion discussions-category-specific-pins %}
![Screenshot of the right sidebar of a discussion. The "Pin discussion" option is highlighted with an orange outline.](/assets/images/help/discussions/click-pin-discussion-with-category-pins.png){% else %}
![Screenshot of the right sidebar of a discussion. The "Pin discussion" option is highlighted with an orange outline.](/assets/images/help/discussions/click-pin-discussion.png){% endif %}
![Screenshot of the right sidebar of a discussion. The "Pin discussion" option is highlighted with an orange outline.](/assets/images/help/discussions/click-pin-discussion-with-category-pins.png)
1. Optionally, customize the look of the pinned discussion.
1. Click **Pin discussion**.
{% ifversion discussions-category-specific-pins %}
### Pinning a discussion to a category
You can pin up to four important discussions above the list of discussions in a specific category.
@@ -86,7 +80,6 @@ You can pin up to four important discussions above the list of discussions in a
![Screenshot of the right sidebar of a discussion. The "Pin discussion to Q&A" option is outlined in dark orange.](/assets/images/help/discussions/pin-discussion-to-category.png)
1. To confirm, click **Pin to CATEGORY**.
{% endif %}
## Editing a pinned discussion
@@ -95,22 +88,19 @@ Editing a pinned discussion will not change the discussion's category. For more
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
1. In the right sidebar, click **{% octicon "pencil" aria-hidden="true" %} Edit pinned discussion**. {% ifversion discussions-category-specific-pins %}
1. In the right sidebar, click **{% octicon "pencil" aria-hidden="true" %} Edit pinned discussion**.
![Screenshot of the right sidebar of a discussion. The "Edit pinned discussion" option is outlined in dark orange.](/assets/images/help/discussions/edit-pinned-discussion-with-category-pins.png){% endif %}
![Screenshot of the right sidebar of a discussion. The "Edit pinned discussion" option is outlined in dark orange.](/assets/images/help/discussions/edit-pinned-discussion-with-category-pins.png)
1. Customize the look of the pinned discussion.
1. Click **Pin discussion**.
## Unpinning a discussion
{% ifversion discussions-category-specific-pins %}
You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
### Unpinning a globally pinned discussion
You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
{% endif %}
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
@@ -121,8 +111,6 @@ You can unpin a globally pinned discussion. This will not delete the discussion,
1. Read the warning, then click **Unpin discussion**.
{% ifversion discussions-category-specific-pins %}
### Unpinning a discussion from a category
You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
@@ -135,7 +123,6 @@ You can unpin a discussion pinned to a specific category. This will not delete t
![Screenshot of the right sidebar of a discussion. The "Unpin discussion from this category" option is outlined in dark orange.](/assets/images/help/discussions/unpin-discussion-from-category.png)
1. Read the warning, then click **Unpin from this category**.
{% endif %}
## Transferring a discussion
@@ -144,12 +131,9 @@ To transfer a discussion, you must have permissions to create discussions in the
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
1. In the right sidebar, click {% octicon "arrow-right" aria-hidden="true" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
{% ifversion discussions-category-specific-pins %}
1. In the right sidebar, click {% octicon "arrow-right" aria-hidden="true" %}**Transfer this discussion**.
![Screenshot of the right sidebar of a discussion. The "Transfer this discussion" option is outlined in dark orange.](/assets/images/help/discussions/transfer-discussion-with-category-pin.png) {% else %}
![Screenshot of the right sidebar of a discussion. The "Transfer this discussion" option is outlined in dark orange.](/assets/images/help/discussions/click-transfer-discussion.png){% endif %}
![Screenshot of the right sidebar of a discussion. The "Transfer this discussion" option is outlined in dark orange.](/assets/images/help/discussions/transfer-discussion-with-category-pin.png)
1. Select the repository you want to transfer the discussion to. You can also search for repositories. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
1. Click **Transfer discussion**.
@@ -160,14 +144,11 @@ To transfer a discussion, you must have permissions to create discussions in the
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
1. In the right sidebar, click **{% octicon "trash" aria-hidden="true" %} Delete discussion**.
{% ifversion discussions-category-specific-pins %}
![Screenshot of the right sidebar of a discussion. The "Delete discussion" option is outlined in dark orange.](/assets/images/help/discussions/delete-discussion-with-category-pins.png){% endif %}
![Screenshot of the right sidebar of a discussion. The "Delete discussion" option is outlined in dark orange.](/assets/images/help/discussions/delete-discussion-with-category-pins.png)
1. Read the warning, then click **Delete this discussion**.
{% ifversion discussions-closable %}
## Closing a discussion
{% data reusables.discussions.closing-discussions %}
@@ -178,8 +159,6 @@ To transfer a discussion, you must have permissions to create discussions in the
1. At the bottom of the discussion, below the comment box, click **Close discussion**.
1. Optionally, to change the reason for closing the discussion, select the {% octicon "triangle-down" aria-label="The down triangle octicon" %} dropdown next to "Close discussion" and click a reason.
{% endif %}
## Converting issues based on labels
You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure.

14
content/discussions/managing-discussions-for-your-community/moderating-discussions.md
View File

@@ -3,7 +3,9 @@ title: Moderating discussions
intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes %} organization''s contribution guidelines{% endif %}.'
permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
---
@@ -17,15 +19,11 @@ versions:
## Locking discussions
It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/site-policy/github-terms/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion. {% ifversion discussions-lock-allow-reactions %}You can also allow emoji reactions to a locked discussion.{% endif %}
{% ifversion discussions-closable %}
It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/site-policy/github-terms/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion. You can also allow emoji reactions to a locked discussion.
> [!NOTE]
> You can also close a discussion. For more information, see [Closing a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#closing-a-discussion).
{% endif %}
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
1. In the list of discussions, click the discussion you want to lock.
@@ -33,8 +31,8 @@ It's appropriate to lock a conversation when the entire conversation is not cons
![Screenshot of the list of discussions with an unanswered discussion.](/assets/images/help/discussions/unanswered-discussion.png)
1. In the right margin of a discussion, click **Lock conversation**.
1. Read the information about locking conversations.{% ifversion discussions-lock-allow-reactions %}
1. Optionally, to allow emoji reactions while the discussion is locked, select **Allow reactions**.{% endif %}
1. Read the information about locking conversations.
1. Optionally, to allow emoji reactions while the discussion is locked, select **Allow reactions**.
1. To lock the conversation, click **Lock conversation**.
1. When you're ready to unlock the conversation, click **Unlock conversation** in the right margin of a discussion, then click **Unlock conversation**.

4
content/discussions/managing-discussions-for-your-community/syntax-for-discussion-category-forms.md
View File

@@ -3,7 +3,9 @@ title: Syntax for discussion category forms
shortTitle: Syntax for discussion category forms
intro: You can use YAML syntax to define the fields in your discussion category forms.
versions:
feature: discussion-category-forms
fpt: '*'
ghes: '*'
ghec: '*'
---
## About YAML syntax for discussion category forms

4
content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
View File

@@ -3,7 +3,9 @@ title: Viewing insights for your discussions
intro: 'Discussions insights provide data about your discussions'' activity, views, and contributors.'
permissions: Repository administrators and people with maintain access to a repository can view the insights dashboard for discussions in that repository. Repository administrators and people with maintain access to the source repository for organization discussions can view the insights dashboard for discussions in that organization.
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
topics:
- Discussions
shortTitle: View discussions insights

4
content/discussions/quickstart.md
View File

@@ -3,7 +3,9 @@ title: Quickstart for GitHub Discussions
intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository or organization and start conversations with your community.'
allowTitleToDifferFromFilename: true
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
shortTitle: Quickstart
---

4
content/graphql/guides/using-the-graphql-api-for-discussions.md
View File

@@ -2,7 +2,9 @@
title: Using the GraphQL API for Discussions
intro: 'Learn how to use the {% data variables.product.prodname_discussions %} GraphQL API.'
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
shortTitle: Use GraphQL for Discussions
---

3
content/issues/tracking-your-work-with-issues/about-issues.md
View File

@@ -54,12 +54,9 @@ To help contributors open meaningful issues that provide the information that yo
You can @mention collaborators who have access to your repository in an issue to draw their attention to a comment. To link related issues in the same repository, you can type `#` followed by part of the issue title and then clicking the issue that you want to link. To communicate responsibility, you can assign issues. If you find yourself frequently typing the same comment, you can use saved replies.
{% ifversion fpt or ghec %} See [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) and [AUTOTITLE](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users).
{% endif %}
{% ifversion discussions %}
## Comparing issues and discussions
Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} For guidance on when to use an issue or a discussion, see [AUTOTITLE](/get-started/using-github/communicating-on-github).
When a conversation in an issue is better suited for a discussion, you can convert the issue to a discussion.
{% endif %}

4
content/issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md
View File

@@ -97,8 +97,6 @@ You can open a new issue from a specific line or lines of code in a file or pull
{% data reusables.repositories.assign-an-issue-as-project-maintainer %}
{% data reusables.repositories.submit-new-issue %}
{% ifversion discussions %}
## Creating an issue from discussion
People with triage permission to a repository can create an issue from a discussion.
@@ -115,8 +113,6 @@ When you create an issue from a discussion, the contents of the discussion post
{% data reusables.repositories.assign-an-issue-as-project-maintainer %}
{% data reusables.repositories.submit-new-issue %}
{% endif %}
{% ifversion projects-v2-create-issue-modal %}
## Creating an issue from a project

4
content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
View File

@@ -3,7 +3,9 @@ title: Enabling or disabling GitHub Discussions for an organization
intro: 'You can use {% data variables.product.prodname_discussions %} in an organization as a place for your organization to have conversations that aren''t specific to a single repository within your organization.'
permissions: 'Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.'
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
topics:
- Organizations
shortTitle: Organization discussions

4
content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
View File

@@ -5,7 +5,9 @@ redirect_from:
- /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization
permissions: Organization owners can manage discussion creation for repositories owned by the organization.
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
topics:
- Organizations
- Teams

4
content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
View File

@@ -3,7 +3,9 @@ title: Enabling or disabling GitHub Discussions for a repository
intro: 'You can use {% data variables.product.prodname_discussions %} in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.'
permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_discussions %} for the repository.'
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
topics:
- Repositories
redirect_from:

4
content/search-github/searching-on-github/searching-discussions.md
View File

@@ -2,7 +2,9 @@
title: Searching discussions
intro: 'You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers.'
versions:
feature: discussions
fpt: '*'
ghes: '*'
ghec: '*'
topics:
- GitHub search
redirect_from:

2
data/reusables/actions/enable-debug-logging.md
View File

@@ -1,4 +1,2 @@
{% ifversion debug-reruns %}
1. Optionally, to enable runner diagnostic logging and step debug logging for the re-run, select **Enable debug logging**.
1. Click **Re-run jobs**.
{% endif %}

2
data/reusables/actions/github-token-scope-descriptions.md
View File

@@ -11,9 +11,7 @@ Available permissions and details of what each allows an action to do:
| `checks` | Work with check runs and check suites. For example, `checks: write` permits an action to create a check run. For more information, see [AUTOTITLE](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-checks). |
| `contents` | Work with the contents of the repository. For example, `contents: read` permits an action to list the commits, and `contents: write` allows the action to create a release. For more information, see [AUTOTITLE](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-contents). |
| `deployments` | Work with deployments. For example, `deployments: write` permits an action to create a new deployment. For more information, see [AUTOTITLE](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-deployments). |
| {% ifversion discussions %} |
| `discussions` | Work with GitHub Discussions. For example, `discussions: write` permits an action to close or delete a discussion. For more information, see [AUTOTITLE](/graphql/guides/using-the-graphql-api-for-discussions). |
| {% endif %} |
| {% ifversion fpt or ghec %} |
| `id-token` | Fetch an OpenID Connect (OIDC) token. This requires `id-token: write`. For more information, see [AUTOTITLE](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#updating-your-actions-for-oidc) |
| {% endif %} |

2
data/reusables/discussions/marking-a-comment-as-an-answer.md
View File

@@ -4,7 +4,7 @@ When you mark a question as an answer, {% data variables.product.product_name %}
![Screenshot of a comment marked as the answer to a discussion.](/assets/images/help/discussions/comment-marked-as-answer.png)
{% ifversion discussions-mark-threaded-comment-as-answer %}You can also mark a threaded comment (in response to a comment) as the answer to a discussion. You can't mark a minimized comment as the answer to a discussion. {% else %}You can't mark a threaded comment in response to a comment as the answer to a discussion. You also can't mark a minimized comment as the answer to a discussion.{% endif %}
You can also mark a threaded comment (in response to a comment) as the answer to a discussion. You can't mark a minimized comment as the answer to a discussion.
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}

3
data/reusables/organizations/additional-permissions.md
View File

@@ -1,5 +1,3 @@
{% ifversion discussions %}
### Discussions
* Create a discussion category
@@ -10,7 +8,6 @@
* Convert issues to discussions
For more information, see [AUTOTITLE](/discussions).
{% endif %}
### Issue and Pull Requests