Skip to content

Conversation

@yapple
Copy link

@yapple yapple commented Dec 17, 2025

Pull Request Description

[Please provide a clear and concise description of your changes here]

Related Issues

Resolves: #[Insert issue number(s)]

Important: Before submitting, please complete the description above and review the checklist below.


Contribution Guidelines (Expand for Details)

We appreciate your contribution to PrisKV! To ensure a smooth review process and maintain high code quality, please adhere to the following guidelines:

Pull Request Title Format

Your PR title should start with one of these prefixes to indicate the nature of the change:

  • [Bug]: Corrections to existing functionality
  • [CI]: Changes to build process or CI pipeline
  • [Docs]: Updates or additions to documentation
  • [API]: Modifications to PrisKV's API or interface
  • [CLI]: Changes or additions to the Command Line Interface
  • [Misc]: For changes not covered above (use sparingly)

Note: For changes spanning multiple categories, use multiple prefixes in order of importance.

Submission Checklist

  • PR title includes appropriate prefix(es)
  • Changes are clearly explained in the PR description
  • New and existing tests pass successfully
  • Code adheres to project style and best practices
  • Documentation updated to reflect changes (if applicable)
  • Thorough testing completed, no regressions introduced

By submitting this PR, you confirm that you've read these guidelines and your changes align with the project's contribution standards.

@yapple yapple force-pushed the feature/pin branch 2 times, most recently from bce6a5e to 03b0c45 Compare December 17, 2025 12:50
@yapple yapple force-pushed the feature/pin branch 3 times, most recently from 7275ee8 to ddda176 Compare January 6, 2026 03:57
@yapple yapple changed the title client initially support pin/unpin [WIP] client initially support pin/unpin Jan 6, 2026
@yapple yapple changed the title [WIP] client initially support pin/unpin [WIP] support pin/unpin feature Jan 6, 2026
@yapple yapple force-pushed the feature/pin branch 2 times, most recently from 4c5f262 to 0548b78 Compare January 8, 2026 03:37
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.

1 participant