Skip to content

Conversation

azjezz
Copy link
Owner

@azjezz azjezz commented Feb 27, 2025

No description provided.

Signed-off-by: azjezz <azjezz@protonmail.com>
Signed-off-by: azjezz <azjezz@protonmail.com>
Signed-off-by: azjezz <azjezz@protonmail.com>
@azjezz azjezz added Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Review Needed The issue has a PR attached to it which needs to be reviewed. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity Type: Enhancement Most issues will probably ask for additions or changes. labels Feb 27, 2025
@azjezz azjezz requested a review from veewee February 27, 2025 05:13
@azjezz azjezz self-assigned this Feb 27, 2025
@coveralls
Copy link

Pull Request Test Coverage Report for Build 13559404829

Details

  • 9 of 9 (100.0%) changed or added relevant lines in 3 files are covered.
  • 2 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.04%) to 98.447%

Files with Coverage Reduction New Missed Lines %
src/Psl/DateTime/Internal/high_resolution_time.php 2 80.95%
Totals Coverage Status
Change from base Build 13511997858: -0.04%
Covered Lines: 5389
Relevant Lines: 5474

💛 - Coveralls

@azjezz azjezz merged commit 78078f2 into next Mar 3, 2025
34 checks passed
@azjezz azjezz deleted the chore/update-mago-013 branch March 3, 2025 00:07
devnix pushed a commit to devnix/psl that referenced this pull request Mar 24, 2025
* chore: update mago to version 0.13

Signed-off-by: azjezz <azjezz@protonmail.com>

* chore: re-format the codebase using the latest mago

Signed-off-by: azjezz <azjezz@protonmail.com>

* chore: migrate from `mago fix` to `mago lint --fix`

Signed-off-by: azjezz <azjezz@protonmail.com>

---------

Signed-off-by: azjezz <azjezz@protonmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Review Needed The issue has a PR attached to it which needs to be reviewed. Type: Enhancement Most issues will probably ask for additions or changes. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants