Skip to content

Conversation

@github-actions
Copy link
Contributor

Documentation Updates - 2026-02-12

This PR updates the documentation based on features merged in the last 24 hours.

Features Documented

Changes Made

  • Updated docs/src/content/docs/reference/safe-outputs.md to document the base-branch field
    • Added field to the YAML example with comment
    • Provided explanation of the field's purpose and default behavior
    • Included a practical use case example showing cross-repository PR creation targeting a non-default branch

Merged PRs Referenced

Summary

The base-branch field allows workflows to specify which branch a pull request should target. This is particularly valuable for cross-repository workflows that need to create PRs targeting non-default branches (such as vnext, release/*, or staging branches).

The documentation update includes:

  • Configuration syntax in the main example
  • Clear explanation of when the field defaults to github.ref_name
  • Real-world use case showing a workflow in org/engineering creating PRs in org/docs targeting the vnext branch

The documentation follows the Diátaxis framework (Reference type), maintains the neutral technical tone, and provides minimal but complete examples as specified in the documentation guidelines.

AI generated by Daily Documentation Updater

  • expires on Feb 13, 2026, 8:28 AM UTC

Add documentation for the new base-branch configuration option in the
create-pull-request safe output. This field allows workflows to specify
which branch a pull request should target, particularly useful for
cross-repository workflows targeting non-default branches.

Changes:
- Add base-branch field to create-pull-request YAML example
- Document default behavior (defaults to github.ref_name)
- Include use case example for cross-repo PR targeting vnext branch

Related: #15089

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@github-actions github-actions bot added automation documentation Improvements or additions to documentation labels Feb 12, 2026
@pelikhan pelikhan merged commit 9e6d71a into main Feb 12, 2026
@pelikhan pelikhan deleted the docs/update-base-branch-field-2026-02-12-419463e98555c3c2 branch February 12, 2026 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant