Merge pull request #34981 from github/repo-sync

Repo sync

.github/workflows/azure-prod-build-deploy.yml

@@ -66,6 +66,7 @@ jobs:
       - name: 'Create Azure Container Registry Token'
         env:
           CONTAINER_REGISTRY_SERVER: ${{ secrets.PROD_REGISTRY_SERVER }}
+          CONTAINER_REPO: ${{ github.repository }}
         run: npm run create-acr-token
 
       - name: 'Docker login'

content/actions/sharing-automations/reusing-workflows.md

@@ -136,7 +136,7 @@ You can define inputs and secrets, which can be passed from the caller workflow
            required: true
            type: string
        secrets:
-         envPAT:
+         personal_access_token:
            required: true
    ```
 
@@ -160,22 +160,22 @@ You can define inputs and secrets, which can be passed from the caller workflow
    jobs:
      reusable_workflow_job:
        runs-on: ubuntu-latest
-       environment: production
        steps:
        - uses: actions/labeler@v4
          with:
-           repo-token: ${{ secrets.envPAT }}
+           repo-token: ${{ secrets.personal_access_token }}
            configuration-path: ${{ inputs.config-path }}
    ```
 
    {% endraw %}
-   In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job.
 
-   {% note %}
+   In the example above, `personal_access_token` is a secret that's defined at the repository or organization level.
 
-   **Note**: Environment secrets are {% ifversion fpt or ghec %}encrypted {% endif %}strings that are stored in an environment that you've defined for a repository. Environment secrets are only available to workflow jobs that reference the appropriate environment. For more information, see "[AUTOTITLE](/actions/deployment/targeting-different-environments/managing-environments-for-deployment#environment-secrets)."
+   {% warning %}
 
-   {% endnote %}
+   **Warning**: Environment secrets cannot be passed from the caller workflow as `on.workflow_call` does not support the `environment` keyword. If you include `environment` in the reusable workflow at the job level, the environment secret will be used, and not the secret passed from the caller workflow. For more information, see "[AUTOTITLE](/actions/deployment/targeting-different-environments/managing-environments-for-deployment#environment-secrets)" and "[AUTOTITLE](/actions/writing-workflows/workflow-syntax-for-github-actions#onworkflow_call)".
+
+   {% endwarning %}
 
 1. Pass the input or secret from the caller workflow.
 
@@ -361,7 +361,7 @@ jobs:
   workflowB-calls-workflowC:
     uses: different-org/example-repo/.github/workflows/C.yml@main
     secrets:
-      envPAT: ${{ secrets.envPAT }} # pass just this secret
+      repo-token: ${{ secrets.person_access_token }} # pass just this secret
 ```
 
 {% endraw %}

content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs.md

@@ -26,16 +26,16 @@ library: # set to true if the pack is a library. Set to false or omit for a quer
 name: <scope>/<pack>
 version: <x.x.x>
 description: <Description to publish with the package>
-default-suite: # optional, one or more queries in the pack to run by default
+defaultSuite: # optional, one or more queries in the pack to run by default
     - query: <relative-path>/query-file>.ql
-default-suite-file: default-queries.qls # optional, a pointer to a query-suite in this pack
+defaultSuiteFile: default-queries.qls # optional, a pointer to a query-suite in this pack
 license: # optional, the license under which the pack is published
 dependencies: # map from CodeQL pack name to version range
 ```
 
 * `name:` must follow the `<scope>/<pack>` format, where `<scope>` is the {% data variables.product.prodname_dotcom %} organization that you will publish to and `<pack>` is the name for the pack.
 
-* A maximum of one of `default-suite` or `default-suite-file` is allowed. These are two different ways to define a default query suite to be run, the first by specifying queries directly in the qlpack.yml file and the second by specifying a query suite in the pack.
+* A maximum of one of `defaultSuite` or `defaultSuiteFile` is allowed. These are two different ways to define a default query suite to be run, the first by specifying queries directly in the qlpack.yml file and the second by specifying a query suite in the pack.
 
 ## Running `codeql pack publish`
 

content/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-organization.md

@@ -49,7 +49,7 @@ Alternatively, you can set up a self-serve workflow using the API. See "[Add tea
 
 Enhance the {% data variables.product.prodname_copilot_short %} experience for your organization by:
 
-* **Indexing repositories** to improve {% data variables.product.prodname_copilot_short %}'s responses relating to {% data variables.product.prodname_dotcom %} repositories _({% data variables.product.prodname_copilot_enterprise_short %} only)_. See "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/indexing-repositories-for-copilot-chat)."
+* **Indexing repositories** to improve {% data variables.product.prodname_copilot_short %}'s responses relating to {% data variables.product.prodname_dotcom %} repositories. See "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/indexing-repositories-for-copilot-chat)."
 * **Setting up knowledge bases** for use with {% data variables.product.prodname_copilot_chat_short %} _({% data variables.product.prodname_copilot_enterprise_short %} only)_. See "[AUTOTITLE](/enterprise-cloud@latest/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/managing-copilot-knowledge-bases)."
 * **Fine tuning {% data variables.product.prodname_copilot_short %}** by creating a custom large language model. See "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/customizing-copilot-for-your-organization/creating-a-custom-model-for-github-copilot)."
 * **Installing {% data variables.product.prodname_copilot_extensions_short %}** to integrate other tools with {% data variables.product.prodname_copilot_chat_short %}. See "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/installing-github-copilot-extensions-for-your-organization)."