Skip to content
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.

Sign up for GitHub

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

Jump to bottom

chore: remove Psl\sequence function #519

Merged
merged 1 commit into from
Mar 5, 2025
Merged

chore: remove Psl\sequence function #519

merged 1 commit into from
Mar 5, 2025

Conversation

azjezz
Copy link
Owner

@azjezz azjezz commented Mar 5, 2025

No description provided.

@azjezz
chore: remove Psl\sequence function
150e08b 
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: Completed Nothing further to be done with this issue. Awaiting to be closed by the requestor out of politeness Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity Type: BC Break A change that will result in a backward compatibility break in the public API. labels Mar 5, 2025
@azjezz azjezz self-assigned this Mar 5, 2025
@coveralls
Copy link

Pull Request Test Coverage Report for Build 13666994400

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.001%) to 98.468%
Totals Coverage Status
Change from base Build 13666899782: -0.001%
Covered Lines: 5464
Relevant Lines: 5549
💛 - Coveralls

@azjezz azjezz merged commit 8d2592d into next Mar 5, 2025
27 of 28 checks passed
devnix pushed a commit to devnix/psl that referenced this pull request Mar 24, 2025
@azjezz @devnix
chore: remove Psl\sequence function (azjezz#519)
22606a7 
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
Reviewers
No reviews
Assignees

@azjezz azjezz

Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Completed Nothing further to be done with this issue. Awaiting to be closed by the requestor out of politeness Type: BC Break A change that will result in a backward compatibility break in the public API. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@azjezz @coveralls