From 0830966efe5490fc199d134b9d44e855692cb76e Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 12 Feb 2026 10:18:01 +0000 Subject: [PATCH] docs: add base-branch term to glossary Add glossary entry for the base-branch configuration field that was introduced in PR #15089. This field allows specifying target branches for cross-repository pull requests, particularly useful for targeting non-default branches like vnext or release branches. --- docs/src/content/docs/reference/glossary.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/src/content/docs/reference/glossary.md b/docs/src/content/docs/reference/glossary.md index 3a9889ec01..e542229a22 100644 --- a/docs/src/content/docs/reference/glossary.md +++ b/docs/src/content/docs/reference/glossary.md @@ -158,6 +158,17 @@ safe-outputs: allowed-exts: [.png, .jpg, .svg] # allowed extensions ``` +### Base Branch + +A configuration field in the `create-pull-request` safe output that specifies which branch the pull request should target. Defaults to `github.ref_name` (the triggering branch) if not specified. Particularly useful for cross-repository pull requests that need to target non-default branches like `vnext`, `release/v1.0`, or feature branches. + +```yaml +safe-outputs: + create-pull-request: + target-repo: "owner/other-repo" + base-branch: "vnext" # Target vnext branch instead of main +``` + ### Minimize Comment A safe output capability that allows workflows to hide or minimize GitHub comments without requiring write permissions. When minimized, comments are classified as SPAM. Requires GraphQL node IDs (format: `IC_kwDOABCD123456`) to identify comments. Useful for content moderation workflows.