Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@Datvite
Copy link
Contributor

@Datvite Datvite commented Oct 25, 2025

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.

Please remove options that are not relevant
Type of change: bug fix, new feature, refactor, or something else?

What

What does the PR do?

Why

Why this PR is needed?

Fixes # (issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have explained the purpose of this PR.
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the README/documentation
  • Any dependent changes have been merged and published in downstream modules
  • Informed of breaking changes, testing and migrations (if applicable).
  • Attached screenshots (if applicable).

By submitting this pull request, I confirm that my contribution is made under the terms of the AGPL-3.0 License.

@kurid3v kurid3v merged commit b42870d into CHT-OJ:master Oct 27, 2025
1 of 3 checks passed
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