Skip to content

Conversation

bsipocz
Copy link
Member

@bsipocz bsipocz commented Sep 7, 2025

No description provided.

@bsipocz bsipocz added this to the 0.5 milestone Sep 7, 2025
Copy link

codecov bot commented Sep 7, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (32b3b11) to head (0281377).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #159   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines          108       108           
  Branches        19        19           
=========================================
  Hits           108       108           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Collaborator

@effigies effigies left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable, but I'm not sure we use Github's release notes generator, so I don't know that this will have an effect. Will defer to others...

Co-authored-by: Chris Markiewicz <[email protected]>
@bsipocz
Copy link
Member Author

bsipocz commented Sep 7, 2025

I've seen the bot PRs mentioned in previous changelogs, thus the PR :)

@stefanv
Copy link
Member

stefanv commented Oct 1, 2025

@lagru We already exclude "dependabot[bot]" from the contributors list, but is there a way to ignore all those PRs as well?

As you see in this PR, GitHub has the changelog.exclude.authors configuration.

@lagru
Copy link
Member

lagru commented Oct 2, 2025 via email

@bsipocz
Copy link
Member Author

bsipocz commented Oct 2, 2025

I wonder if adding this file to the org level .github repo would make it affective for every repos; I didn't really get a clear answer to that question when asked it on the github maintainers' forum and the docs is useless.

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

Successfully merging this pull request may close these issues.

4 participants