Skip to content

fix: add filter-by-commitish option to release drafter config#16

Merged
jescalada merged 1 commit intorelease/1.1from
main
May 4, 2026
Merged

fix: add filter-by-commitish option to release drafter config#16
jescalada merged 1 commit intorelease/1.1from
main

Conversation

@jescalada
Copy link
Copy Markdown
Owner

Adding the missing option since release/1.1 is failing to generate the 1.1.1 release

@jescalada jescalada merged commit 89d4088 into release/1.1 May 4, 2026
15 of 25 checks passed
@github-actions github-actions Bot added the fix label May 4, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 4, 2026

🔒 Automated Security Review

Security Review - No Issues Found

This PR adds a configuration option filter-by-commitish: true to the Release Drafter configuration file. No security concerns identified - this is a standard configuration change for release automation tooling.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 4, 2026

Thanks for the contribution! I noticed a few things that need attention:

Description clarity: The current description is quite brief. Could you provide more details about:

  • What the filter-by-commitish option does
  • Why it's needed for the release process
  • What specific behavior changes with this addition

Issue link: I don't see a linked issue in the description. Per our contributing guidelines, please either:

  • Link an existing issue using "Fixes #N", "Closes #N", or "Resolves #N"
  • Or create a new issue describing the problem this PR solves

Contributing guidelines: According to our CONTRIBUTING.md, the first step should be to "Check for existing issues: Search open issues before starting work. If none exists, create one describing the change."

A more detailed description will help reviewers understand the context and ensure this change aligns with the project's goals.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant