Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Improve Documentation for YAML and CLI Options

Open
#312 8 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 2 days

@OdenTakashi is already working on this.

Since Apr 5, 2026.

Assessment

This issue has not been assessed yet.

Description

Thanks for taking care of the maintenance. 🚀

Background

Currently, the README documents only the configuration options that can be passed via the CLI.
However, there are additional options defined in the YAML configuration file that cannot be configured through the CLI, and these options are not comprehensively documented.

Problem

This results in a discoverability issue:

  • Some options are available only via YAML and are not mentioned in the README.
  • Newly added YAML-only options are difficult to notice.
  • Existing options may be unintentionally overlooked.
  • This may lead to duplicate or redundant feature proposals.

For example, the ignore_multi_database_name option can be configured via YAML, but it is not documented in the README.
Because it was not easily discoverable, a PR was submitted proposing a similar new option: https://github.com/drwl/annotaterb/pull/291#issuecomment-3497296456

Proposal

To improve clarity and prevent confusion, I propose adding a comprehensive list of all available configuration options to the README — including both CLI and YAML options.

Possible Idea

As a possible idea, we could introduce a single Markdown table summarizing all options in one place.

Example:

YAML Option CLI Option Default Description
include_version --show-migration false Adds the current migration version to the annotation

This approach would:

  • Improve discoverability
  • Make configuration options easier to understand
  • Reduce the likelihood of duplicate feature proposals
  • Provide a clear reference for contributors and users

If there are other suggestions or better ways to organize this, I’d be happy to hear them.

Expected Outcome

By documenting all configuration options in a structured and centralized format, the project will become:

  • More transparent
  • Easier to contribute to
  • Less prone to confusion regarding existing functionality
Dominant language
Ruby
Stars
624
Forks
95
Avg merge
1d 21h
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from drwl/annotaterb

All issues in drwl/annotaterb

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.