Add pull-request-header configuration option#81
Merged
Conversation
Replace the local CI definitions with thin caller stubs that delegate to OneLiteFeatherNET/workflows@v2. Behaviour is preserved (Java 25, three-OS matrix on PRs, Maven publish on tag, release-please on main). Note: depends on workflows v2.0.0 being tagged before this PR is merged.
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.
Summary
Added the
pull-request-headerconfiguration option to the release-please configuration file.Changes
"pull-request-header": ""torelease-please-config.jsonDetails
This change enables users to customize or disable the default header that appears in automatically generated release pull requests. The empty string value suggests this can be set to custom text or left empty to omit the header entirely.
https://claude.ai/code/session_015oqxWHjUhVE62udCVbRHDj