Skip to content

Commit 8bd8e75

Browse files
docs-botdocs-bot
authored
Merge pull request #39338 from github/repo-sync
Repo sync
2 parents e84e477 + 370b4e4 commit 8bd8e75

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

50 files changed

+40976
-8422
lines changed

‎content/actions/concepts/workflows-and-actions/about-workflows.md

Lines changed: 0 additions & 208 deletions
This file was deleted.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ versions:
66
ghes: '*'
77
ghec: '*'
88
children:
9-
- /about-workflows
9+
- /workflows
1010
- /variables
1111
- /avoiding-duplication
1212
- /reusable-workflows

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

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
title: Workflows
3+
shortTitle: Workflows
4+
intro: 'Get a high-level overview of {% data variables.product.prodname_actions %} workflows, including triggers, syntax, and advanced features.'
5+
versions:
6+
fpt: '*'
7+
ghes: '*'
8+
ghec: '*'
9+
type: overview
10+
redirect_from:
11+
- /articles/configuring-workflows
12+
- /actions/learn-github-actions/managing-complex-workflows
13+
- /actions/using-workflows/advanced-workflow-features
14+
- /actions/using-workflows/about-workflows
15+
- /actions/writing-workflows/about-workflows
16+
- /actions/concepts/use-cases/using-github-actions-for-project-management
17+
- /actions/concepts/workflows-and-actions/about-workflows
18+
topics:
19+
- Workflows
20+
layout: inline
21+
---
22+
23+
## About workflows
24+
25+
{% data reusables.actions.about-workflows-long %}
26+
27+
## Workflow basics
28+
29+
A workflow must contain the following basic components:
30+
31+
1. One or more _events_ that will trigger the workflow.
32+
1. One or more _jobs_, each of which will execute on a _runner_ machine and run a series of one or more _steps_.
33+
1. Each step can either run a script that you define or run an action, which is a reusable extension that can simplify your workflow.
34+
35+
For more information on these basic components, see [AUTOTITLE](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions).
36+
37+
![Diagram of an event triggering Runner 1 to run Job 1, which triggers Runner 2 to run Job 2. Each of the jobs is broken into multiple steps.](/assets/images/help/actions/overview-actions-simple.png)
38+
39+
## Workflow triggers
40+
41+
{% data reusables.actions.about-triggers %}
42+
43+
For more information, see [AUTOTITLE](/actions/using-workflows/triggering-a-workflow).
44+
45+
## Next steps
46+
47+
To build your first workflow, see [AUTOTITLE](/actions/tutorials/creating-an-example-workflow).

‎content/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ topics:
1919
- SSO
2020
---
2121

22-
**Before** following the steps in this article, make sure that your enterprise uses **managed users**. You can do so by checking whether your enterprise view has the "Users managed by ACCOUNT NAME" header bar at the top of the screen. If you see this, your enterprise uses **managed users** and you can follow the steps in this article.
22+
**Before** following the steps in this article, make sure that your enterprise uses **managed users** and that you are signed in as the setup user whose username is your enterprise's shortcode suffixed with `_admin`. You can verify you are signed in with the correct user by checking whether your enterprise view has the "Viewing as SHORTCODE_admin" header bar at the top of the screen. If you see this, you are signed in with the correct user and you can follow the steps in this article. For more information about the setup user, see [AUTOTITLE](/admin/managing-iam/understanding-iam-for-enterprises/getting-started-with-enterprise-managed-users).
2323

2424
If your enterprise uses **personal accounts**, you must follow a different process to configure SAML single sign-on. See [AUTOTITLE](/admin/managing-iam/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise).
2525

‎content/copilot/how-tos/chat/asking-github-copilot-questions-in-your-ide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -295,7 +295,7 @@ Use agent mode when you have a specific task in mind and want to enable {% data
295295
1. Submit a prompt. In response to your prompt, {% data variables.product.prodname_copilot_short %} streams the edits in the editor, updates the working set, and if necessary, suggests terminal commands to run.
296296
1. Review the changes. If {% data variables.product.prodname_copilot_short %} suggested terminal commands, confirm whether or not {% data variables.product.prodname_copilot_short %} can run them. In response, {% data variables.product.prodname_copilot_short %} iterates and performs additional actions to complete the task in your original prompt.
297297

298-
When you use agent mode, {% data variables.product.prodname_copilot_short %} may make multiple premium requests to complete a single task. This includes both user-initiated prompts and follow-up actions {% data variables.product.prodname_copilot_short %} takes on your behalf. The total premium requests used will depend on the complexity of the task, the number of steps involved, and the model selected. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/monitoring-usage-and-entitlements/avoiding-unexpected-copilot-costs).
298+
When you use {% data variables.copilot.copilot_agent_short %} mode, each prompt you enter counts as one premium request, multiplied by the model’s multiplier. For example, if you're using the included model—which has a multiplier of 0—your prompts won’t consume any premium requests. {% data variables.product.prodname_copilot_short %} may take several follow-up actions to complete your task, but these follow-up actions do **not** count toward your premium request usage. Only the prompts you enter are billed—tool calls or background steps taken by the agent are not charged.
299299

300300
## Using images in {% data variables.copilot.copilot_chat_short %}
301301

‎data/release-notes/enterprise-server/3-14/15.yml

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
date: '2025-07-15'
2+
sections:
3+
security_fixes:
4+
- |
5+
**HIGH**: An incorrect authorization vulnerability allowed unauthorized read access to the contents of internal repositories for contractor accounts when the Contractors API feature was enabled. The Contractors API is a rarely-enabled feature in private preview. Following this fix, contractor account access to internal repositories via the API will be correctly blocked unless they have an alternate grant. GitHub has requested CVE ID [CVE-2025-6981](https://www.cve.org/cverecord?id=CVE-2025-6981) for this vulnerability.
6+
- |
7+
Packages have been updated to the latest security versions.
8+
bugs:
9+
- |
10+
Applying a new GitHub Enterprise Server license using the Management Console would sometimes fail with a HTTP 500 error.
11+
- |
12+
During Git push operations in a HA configuration, it was possible under rare circumstances for the primary voting replica of a repository to become incorrectly marked as out of sync with the other replicas and in need of repair, causing the repository to become unavailable.
13+
changes:
14+
- |
15+
Site administrators can now set `innodb_buffer_pool_size` in megabytes for MySQL using `ghe-config mysql.innodb-buffer-pool-size VALUE`.
16+
known_issues:
17+
- |
18+
During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
19+
- |
20+
If the root site administrator is locked out of the Management Console after failed login attempts, the account does not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)."
21+
- |
22+
On an instance with the HTTP `X-Forwarded-For` header configured for use behind a load balancer, all client IP addresses in the instance's audit log erroneously appear as 127.0.0.1.
23+
- |
24+
{% data reusables.release-notes.large-adoc-files-issue %}
25+
- |
26+
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
27+
- |
28+
When following the steps for [Replacing the primary MySQL node](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-the-primary-mysql-node), step 14 (running `ghe-cluster-config-apply`) might fail with errors. If this occurs, re-running `ghe-cluster-config-apply` is expected to succeed.
29+
- |
30+
Running a config apply as part of the steps for [Replacing a node in an emergency](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-a-node-in-an-emergency) may fail with errors if the node being replaced is still reachable. If this occurs, shutdown the node and repeat the steps.
31+
- |
32+
{% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %}
33+
- |
34+
When restoring data originally backed up from a 3.13 or greater appliance version, the Elasticsearch indices need to be reindexed before some of the data will show up. This happens via a nightly scheduled job. It can also be forced by running `/usr/local/share/enterprise/ghe-es-search-repair`.
35+
- |
36+
An organization-level code scanning configuration page is displayed on instances that do not use GitHub Advanced Security or code scanning.
37+
- |
38+
In the header bar displayed to site administrators, some icons are not available.
39+
- |
40+
When enabling automatic update checks for the first time in the Management Console, the status is not dynamically reflected until the "Updates" page is reloaded.
41+
- |
42+
When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
43+
- |
44+
After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance.
45+
- |
46+
After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows.
47+
- |
48+
Unexpected elements may appear in the UI on the repo overview page for locked repositories.

0 commit comments

Comments
 (0)