Skip to content

[docs] Update documentation for features from 2026-02-23 #17830

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 1 commit into from
Feb 23, 2026
Merged

[docs] Update documentation for features from 2026-02-23 #17830

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/src/content/docs/guides/packaging-imports.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,9 @@ Use `--name`, `--pr`, `--force`, `--engine`, or `--verbose` flags to customize i
> [!NOTE]
> Check carefully that the workflow comes from a trusted source and is appropriate for your use in your repository. Review the workflow's content and understand what it does before adding it to your repository.

> [!NOTE]
> Workflows marked with `private: true` in their frontmatter cannot be added to other repositories. Attempting to do so will fail with an error. See [Private Workflows](/gh-aw/reference/frontmatter/#private-workflows-private) for details.

## Updating Workflows

When you add a workflow, a tracking `source:` entry remembers where it came from. You can keep workflows synchronized with their source repositories:
Expand Down
19 changes: 19 additions & 0 deletions docs/src/content/docs/reference/frontmatter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,25 @@ Tracks workflow origin in format `owner/repo/path@ref`. Automatically populated
source: "githubnext/agentics/workflows/ci-doctor.md@v1.0.0"
```

### Private Workflows (`private:`)

Mark a workflow as private to prevent it from being installed into other repositories via `gh aw add`.
Copy link

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency with other boolean fields like strict: (line 354), consider mentioning the default value. The field defaults to false, meaning workflows are not private unless explicitly marked. This could be added to line 59, for example: "Mark a workflow as private to prevent it from being installed into other repositories via gh aw add. Defaults to false."

Suggested change
Mark a workflow as private to prevent it from being installed into other repositories via `gh aw add`.
Mark a workflow as private to prevent it from being installed into other repositories via `gh aw add`. Defaults to `false`.

Copilot uses AI. Check for mistakes.

```yaml wrap
private: true
```

When `private: true` is set, attempting to add the workflow from another repository will fail with an error:

```
workflow 'owner/repo/internal-tooling' is private and cannot be added to other repositories
```

Use this field for internal tooling, sensitive automation, or workflows that depend on repository-specific context and are not intended for external reuse.

> [!NOTE]
> The `private:` field only blocks installation via `gh aw add`. It does not affect the visibility of the workflow file itself — that is controlled by your repository's access settings.

### Labels (`labels:`)

Optional array of strings for categorizing and organizing workflows. Labels are displayed in `gh aw status` command output and can be filtered using the `--label` flag.
Expand Down