Merge pull request #39377 from github/repo-sync

Repo sync

Author: docs-bot

.github/workflows/sync-graphql.yml

@@ -17,11 +17,16 @@ jobs:
   update_graphql_files:
     if: github.repository == 'github/docs-internal'
     runs-on: ubuntu-latest
+    outputs:
+      ignored-changes: ${{ steps.sync.outputs.ignored-changes }}
+      ignored-count: ${{ steps.sync.outputs.ignored-count }}
+      ignored-types: ${{ steps.sync.outputs.ignored-types }}
     steps:
       - name: Checkout
         uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
       - uses: ./.github/actions/node-npm-setup
       - name: Run updater scripts
+        id: sync
         env:
           # need to use a token from a user with access to github/github for this step
           GITHUB_TOKEN: ${{ secrets.DOCS_BOT_PAT_BASE }}
@@ -70,3 +75,22 @@ jobs:
         with:
           slack_channel_id: ${{ secrets.DOCS_ALERTS_SLACK_CHANNEL_ID }}
           slack_token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }}
+
+  notify_ignored_changes:
+    if: github.repository == 'github/docs-internal' && needs.update_graphql_files.outputs.ignored-count > 0 && github.event_name != 'workflow_dispatch'
+    needs: update_graphql_files
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+      - uses: ./.github/actions/slack-alert
+        with:
+          slack_channel_id: ${{ secrets.DOCS_ALERTS_SLACK_CHANNEL_ID }}
+          slack_token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }}
+          color: warning
+          message: |
+            ⚠️ GraphQL Sync found ${{ needs.update_graphql_files.outputs.ignored-count }} ignored change types: ${{ needs.update_graphql_files.outputs.ignored-types }}
+
+            These change types are not in CHANGES_TO_REPORT and were silently ignored. Consider reviewing if they should be added to the changelog.
+
+            See workflow run: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}

content/actions/concepts/billing-and-usage.md

@@ -0,0 +1,62 @@
+---
+title: 'Billing and usage'
+intro: 'There are usage limits for {% data variables.product.prodname_actions %} workflows. Usage charges apply to repositories that go beyond the amount of free minutes and storage for a repository.'
+redirect_from:
+  - /actions/getting-started-with-github-actions/usage-and-billing-information-for-github-actions
+  - /actions/reference/usage-limits-billing-and-administration
+  - /actions/learn-github-actions/usage-limits-billing-and-administration
+  - /actions/administering-github-actions/usage-limits-billing-and-administration
+  - /actions/concepts/overview/usage-limits-billing-and-administration
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Billing
+---
+
+## About billing for {% data variables.product.prodname_actions %}
+
+{% ifversion fpt or ghec %}
+{% data reusables.actions.actions-billing %} For more information, see [AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions).
+{% else %}
+{% data variables.product.prodname_actions %} usage is free for {% data variables.product.prodname_ghe_server %} instances that use self-hosted runners. For more information, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners).
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+## Availability
+
+{% data variables.product.prodname_actions %} is available on all {% data variables.product.prodname_dotcom %} products, but {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. {% data reusables.gated-features.more-info %}
+
+{% endif %}
+
+## Usage limits and policy
+
+There are several limits on {% data variables.product.prodname_actions %} usage when using {% data variables.product.prodname_dotcom %}-hosted runners. See [AUTOTITLE](/actions/reference/actions-limits).
+
+In addition to the usage limits, you must ensure that you use {% data variables.product.prodname_actions %} within the [GitHub Terms of Service](/free-pro-team@latest/site-policy/github-terms/github-terms-of-service). For more information on {% data variables.product.prodname_actions %}-specific terms, see the [GitHub Additional Product Terms](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#a-actions-usage).
+
+{% ifversion fpt or ghec %}
+
+## {% data variables.product.prodname_actions %} usage metrics
+
+Organization owners and users with the "View organization Actions metrics" permission can view {% data variables.product.prodname_actions %} usage metrics for their organization. These metrics can help you understand how and where your Actions minutes are being used. For more information, see [AUTOTITLE](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/viewing-usage-metrics-for-github-actions).
+
+When you view usage metrics, it is important to remember that {% data reusables.actions.actions-usage-metrics-not-billing-metrics %}
+
+{% endif %}
+
+## Billing for reusable workflows
+
+If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository.
+
+For more information see, [AUTOTITLE](/actions/using-workflows/reusing-workflows).
+
+## Next steps
+
+You can manage your {% data variables.product.prodname_actions %} usage and retention policies for your repository, organization, or enterprise account. For more information, see:
+* [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)
+* [AUTOTITLE](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)
+* [AUTOTITLE](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)
+* [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)

content/actions/concepts/index.md

@@ -12,6 +12,7 @@ children:
   - /runners
   - /security
   - /about-github-actions-metrics
+  - /billing-and-usage
 redirect_from:
   - /actions/concepts/use-cases
 ---

content/actions/concepts/overview/index.md

@@ -9,5 +9,4 @@ versions:
 children:
   - /about-continuous-deployment-with-github-actions
   - /continuous-integration
-  - /usage-limits-billing-and-administration
 ---

content/actions/concepts/overview/usage-limits-billing-and-administration.md

@@ -0,0 +1,18 @@
+---
+title: Concurrency
+intro: 'Learn about running workflows and jobs simultaneously.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Actions
+  - Workflows
+---
+
+By default, {% data variables.product.prodname_actions %} allows multiple jobs within the same workflow, multiple workflow runs within the same repository, and multiple workflow runs across a repository owner's account to run concurrently. This means that multiple instances of the same workflow or job can run at the same time, performing the same steps.
+
+{% data variables.product.prodname_actions %} also allows you to disable concurrent execution. This can be useful for controlling your account’s or organization’s resources in situations where running multiple workflows or jobs at the same time could cause conflicts or consume more Actions minutes and storage than expected. For example, you might want to prevent multiple deployments from running at the same time, or cancel linters checking outdated commits.
+
+To start controlling concurrency in your own workflows with the `concurrency` keyword, see [AUTOTITLE](/actions/how-tos/writing-workflows/choosing-when-your-workflow-runs/control-the-concurrency-of-workflows-and-jobs).

content/actions/concepts/workflows-and-actions/concurrency.md

@@ -14,6 +14,7 @@ children:
   - /contexts
   - /expressions
   - /deployment-environments
+  - /concurrency
   - /workflow-artifacts
   - /dependency-caching
   - /about-monitoring-workflows

content/actions/concepts/workflows-and-actions/index.md

@@ -19,7 +19,5 @@ children:
   - /passing-information-between-jobs
   - /setting-a-default-shell-and-working-directory
   - /deploying-to-a-specific-environment
-  - /control-the-concurrency-of-workflows-and-jobs
   - /running-variations-of-jobs-in-a-workflow
 ---
-

content/actions/how-tos/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs.md

@@ -0,0 +1,26 @@
+---
+title: Control the concurrency of workflows and jobs
+shortTitle: Control workflow concurrency
+intro: Manage which workflows and jobs can run simultaneously.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+redirect_from:
+  - /actions/using-jobs/using-concurrency
+  - /actions/writing-workflows/choosing-what-your-workflow-does/using-concurrency
+  - /early-access/actions/running-additional-jobs-in-github-actions
+  - /actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs
+  - /actions/how-tos/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs
+---
+
+## Using concurrency in different scenarios
+
+{% data reusables.actions.jobs.section-using-concurrency-jobs %}
+
+{% ifversion github-runner-dashboard %}
+
+## Monitoring your current jobs in your organization or enterprise
+
+{% data reusables.actions.github-hosted-runners-check-concurrency %}
+{% endif %}