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

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

@@ -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 %}

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

@@ -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:

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

@@ -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

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

@@ -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,16 +42,15 @@ 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 %}
 
 For discussions with a question/answer format, an individual comment within the discussion can be marked as the discussion's answer. {% data reusables.discussions.github-recognizes-members %}
 
 {% 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).
 

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

@@ -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: '*'
 ---
 
 

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

@@ -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
 ---
-

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

@@ -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
 ---
 

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

@@ -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: '*'
 ---
 
 

content/discussions/guides/finding-your-discussions.md

@@ -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

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

@@ -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
 ---
 

content/discussions/guides/index.md

@@ -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
 ---
-

content/discussions/index.md

@@ -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'

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

@@ -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

content/discussions/managing-discussions-for-your-community/index.md

@@ -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
 ---
-

content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md

@@ -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,22 +79,19 @@ 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 %}
 1. To the right of a category in the list, click {% octicon "trash" aria-label="The trash icon" %}.
 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 %}