Add allowed-base-branches: [main] to release notes workflow#3813
Merged
Conversation
The safe-outputs policy rejected the PR because base branch override to main wasn't explicitly allowed. Needed because the workflow triggers on release/** branches but PRs should always target main. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
📦 Try the packages from this PRWarning Do not run these scripts without first reviewing the code in this PR. Step 1 — Download the packages bash / macOS / Linux: curl -fsSL https://raw.githubusercontent.com/mono/SkiaSharp/main/scripts/get-skiasharp-pr.sh | bash -s -- 3813PowerShell / Windows: iex "& { $(irm https://raw.githubusercontent.com/mono/SkiaSharp/main/scripts/get-skiasharp-pr.ps1) } 3813"Step 2 — Add the local NuGet source dotnet nuget add source ~/.skiasharp/hives/pr-3813/packages --name skiasharp-pr-3813More options
Or download manually from Azure Pipelines — look for the Remove the source when you're done: dotnet nuget remove source skiasharp-pr-3813 |
github-actions Bot
added a commit
that referenced
this pull request
Apr 29, 2026
Add docs landing page improvement (#3794), note CI and workflow automation improvements (#3755, #3787, #3802, #3805, #3808, #3811, #3812, #3813), and expand highlights paragraph. Community sample fixes by @ramezgerges (#3785, #3790) were already present. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the workflow configuration for generating release notes, focusing on tightening restrictions for pull request creation and making minor maintenance updates. The most significant change is the introduction of an
allowed_base_branches(orallowed-base-branches) restriction, ensuring that documentation pull requests can only target themainbranch. There are also corresponding updates to configuration blocks and metadata references.Workflow restriction and configuration updates
allowed-base-branches: [main]to thecreate_pull_requeststep in.github/workflows/update-release-notes.mdto restrict documentation pull requests to themainbranch.create_pull_requestconfiguration in.github/workflows/update-release-notes.lock.ymlto include"allowed_base_branches":["main"]in both the safe outputs handler and the safe outputs config JSON, enforcing the same restriction in the locked workflow. [1] [2]Maintenance and metadata updates
.github/workflows/update-release-notes.lock.ymlto reflect new content hashes and maintain consistency. [1] [2] [3] [4] [5]These changes ensure that only documentation pull requests targeting the
mainbranch are allowed, improving workflow safety and alignment with repository policies.