Skip to content

docs: refresh hand-maintained README prose and add feature-choice how-to#297

Merged
EffortlessSteven merged 2 commits into
mainfrom
chore/main-docs-pr
Mar 25, 2026
Merged

docs: refresh hand-maintained README prose and add feature-choice how-to#297
EffortlessSteven merged 2 commits into
mainfrom
chore/main-docs-pr

Conversation

@EffortlessSteven

Copy link
Copy Markdown
Member

Summary

  • Refresh hand-maintained documentation prose for README.md and docs/README.md while preserving docs-sync-managed generated blocks.
  • Add docs/how-to/choose-features.md with clear, minimal feature-path guidance.

Validation

  • cargo xtask docs-sync --check

@coderabbitai

coderabbitai Bot commented Mar 25, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@EffortlessSteven has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 54 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 29404d8d-2c0f-48ad-ae5b-16c97d8ba82e

📥 Commits

Reviewing files that changed from the base of the PR and between d3ced09 and 0213d23.

📒 Files selected for processing (3)
  • README.md
  • docs/README.md
  • docs/how-to/choose-features.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/main-docs-pr

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the project's documentation to make it more accessible and informative for users. It includes a comprehensive refresh of existing README files to improve their prose and structure, alongside the introduction of a new guide specifically designed to help users understand and choose the most suitable feature sets for their needs. The changes aim to clarify the purpose and usage of the uselesskey crate, streamlining the onboarding process for new and existing developers.

Highlights

  • Documentation Refresh: The README.md and docs/README.md files have been significantly refreshed, improving clarity, structure, and conciseness of the prose while preserving auto-generated content.
  • New Feature Selection Guide: A new how-to guide, docs/how-to/choose-features.md, has been added to provide clear, minimal guidance on selecting appropriate feature flags for uselesskey based on specific use cases.
  • Improved Readability and Structure: Numerous sections across the main README.md have been rephrased, reorganized, and retitled to enhance the overall readability and user experience, including explanations for 'Why this exists', 'What you get', and 'When not to use this crate'.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request significantly refactors and expands the documentation for the uselesskey project, primarily updating the README.md for improved clarity, organization, and detailed explanations. It also introduces a new guide, docs/how-to/choose-features.md, to assist users in selecting appropriate feature flags. The changes include rephrasing introductory sections, standardizing headings to lowercase, and enhancing explanations for various features and use cases. Feedback suggests reintroducing arrows for better visualization in certificate chain descriptions and ensuring consistent phrasing in feature lists for improved readability.

Comment thread README.md
```

Three-level certificate chains (root CA → intermediate CA → leaf):
Three-level chains (root intermediate leaf):

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The arrows () from the previous version were helpful for visualizing the certificate chain flow. Consider adding them back for clarity. The double space also seems unintentional.

Suggested change
Three-level chains (root intermediate leaf):
Three-level chains (root intermediate leaf):

Comment on lines +10 to +13
- Add `ecdsa` for P-256 / P-384.
- Add `ed25519` for Ed25519 keypairs.
- Add `hmac` for HS256/HS384/HS512 fixtures.
- Add `pgp` for OpenPGP armored/binary artifacts.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For consistency in this list, consider starting each item with "Use" to match the first item.

Suggested change
- Add `ecdsa` for P-256 / P-384.
- Add `ed25519` for Ed25519 keypairs.
- Add `hmac` for HS256/HS384/HS512 fixtures.
- Add `pgp` for OpenPGP armored/binary artifacts.
- Use `ecdsa` for P-256 / P-384.
- Use `ed25519` for Ed25519 keypairs.
- Use `hmac` for HS256/HS384/HS512 fixtures.
- Use `pgp` for OpenPGP armored/binary artifacts.

@EffortlessSteven EffortlessSteven merged commit ab99b90 into main Mar 25, 2026
4 checks passed
@EffortlessSteven EffortlessSteven deleted the chore/main-docs-pr branch April 3, 2026 03:45
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