Skip to content

Bump perltidy from 20240511 to 20250311 #3375

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 5, 2025
Merged

Bump perltidy from 20240511 to 20250311 #3375

merged 3 commits into from
Jun 5, 2025

Conversation

oalders
Copy link
Member

@oalders oalders commented Jun 4, 2025

  • Bump perltidy from 20240511 to 20250311
  • perltidy with version 20250311

Copy link

codecov bot commented Jun 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.36%. Comparing base (e8afe67) to head (634792b).
Report is 18 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3375   +/-   ##
=======================================
  Coverage   73.36%   73.36%           
=======================================
  Files          68       68           
  Lines        2388     2388           
  Branches      335      335           
=======================================
  Hits         1752     1752           
  Misses        508      508           
  Partials      128      128           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@oalders oalders force-pushed the oalders/perltidy branch from e57ff60 to 634792b Compare June 4, 2025 23:30
@oalders oalders added this pull request to the merge queue Jun 5, 2025
Merged via the queue into master with commit 8da5b21 Jun 5, 2025
11 checks passed
@oalders oalders deleted the oalders/perltidy branch June 5, 2025 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants