Skip to content

fix(labrinth): charge user check - #8337

Merged
mergify[bot] merged 1 commit into
mainfrom
fetch/db-charge-ownership-check
Nov 16, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
fetch/db-charge-ownership-check

Conversation

@fetchfern

Copy link
Copy Markdown
Member

Reported-by: Haam

@github-actions

Copy link
Copy Markdown
Contributor

Pull request changelog

App

Added

Changed

Deprecated

Removed

Fixed

Security

Website

Added

Changed

Deprecated

Removed

Fixed

Security

Hosting

Added

Changed

Deprecated

Removed

Fixed

Security

@mergify

mergify Bot commented Nov 15, 2026 •

Copy link
Copy Markdown

Queue requested — the merge queue status continues in this comment ↓.

@fetchfern
fetchfern requested a review from aecsocket November 15, 2026 17:57
@greptile-apps

greptile-apps Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Reviews (1) · Last reviewed commit: "fix(labrinth): DBCharge user ownership c..." · Reviewed by Greptile

@aecsocket

Copy link
Copy Markdown
Contributor

@Mergifyio queue

@mergify

mergify Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

✅ Merged into main as e44cb5e at 11:10 UTC

1 min in the queue, with no time running CI.

So far

2 merge conditions met
  • github-review-approved · required by GitHub branch protection
  • any of · required by GitHub branch protection:
    • check-skipped = Lint and Test
    • check-neutral = Lint and Test
    • check-success = Lint and Test

Times in UTC · dashboard · how the merge queue works

@mergify mergify Bot added the queued label Nov 16, 2026
@mergify
mergify Bot merged commit e44cb5e into main Nov 16, 2026
13 checks passed
@mergify
mergify Bot deleted the fetch/db-charge-ownership-check branch November 16, 2026 11:10
@mergify mergify Bot removed the queued label Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants