8000 Professional changelog (Keep a Changelog), README, CLI help and troubleshooting by rafatahmed · Pull Request #153 · rafatahmed/Flahax · GitHub
[go: up one dir, main page]

Skip to content

Professional changelog (Keep a Changelog), README, CLI help and troubleshooting - #153

Merged
rafatahmed merged 2 commits into
mainfrom
docs/changelog-0.6.0
Oct 23, 2026
Merged

rafatahmed merged 2 commits into
mainfrom
docs/changelog-0.6.0

Conversation

@rafatahmed
@rafatahmed rafatahmed commented Oct 23, 2026 •
Copy link
Copy Markdown
Owner

The owner asked for a professional format, following the standards, for the changelog (every release), the README, the CLI help, and troubleshooting for upgrades. Each part follows a published standard.

Changelog: Keep a Changelog 1.1.0, every release

  • Structure:
    • ## [Unreleased] comes first;
    • every release is headed ## [X.Y.Z] - YYYY-MM-DD; 0.3.0 is marked [YANKED]; 0.6.0 reads - not yet released until the finalize step dates it;
    • every version has a comparison link at the bottom. Dates come from the published releases; 0.1.0 and 0.2.0 use their tag dates.
  • Content:
    • each release opens with a short paragraph: what it is, any breaking change, Python, and known limits;
    • bullets are grouped under the six standard change types only, at most 400 characters each, with issue numbers. "Compatibility and limits" is not a standard type, so it moves into the opening paragraph;
    • 0.5.0, 0.4.0 and 0.3.1 are rewritten from their long paragraphs; their full original text moves unchanged to docs/releases/0.5.0.md, 0.4.0.md and 0.3.1.md, alongside 0.6.0.md and 0.3.0.md.
  • Enforcement:
    • tests/test_changelog.py checks every release: headings, types, bullet length, grouping and links. It finds 28 problems in the previous changelog;
    • CONTRIBUTING states the rule.

CLI help: Command Line Interface Guidelines

  • flahax --help gives:
    • a one-line description of every command (mix, batch, recommend, workflow, ec, size);
    • examples, including a flahax batch example that was run to confirm it works;
    • links to the documentation and to the issue tracker.
  • --interactive is described in the same style as the other options.
  • The start screen (bare flahax) links the documentation.
  • Behaviour is unchanged: the same commands and options, and the same JSON contract.
  • test_help_describes_every_command_with_examples_and_links failed before the change.

Troubleshooting

README: PyPA, PyPI-friendly README

  • Order: what it is and who it is for, installation (install, upgrade, from GitHub), quick start (flahax mix, flahax batch, Python), commands, what it does, documentation, troubleshooting, verification and limits (with the roadmap), contributing (with the code of conduct and security policy), citation, credits, license.
  • Removed:
    • the stale "153 automated tests";
    • in-page links, because PyPI does not create heading anchors.
  • Kept: the Python example (a test runs it), the capability table, the citation, the credits and the license, all unchanged.
  • PyPI: twine check --strict passes on the built wheel and sdist.

Also in this PR

  • The docs build fix: the changelog's link to the detailed notes is a full GitHub URL, because the docs site includes the changelog.

Checks

  • Full suite: 623 tests, including the live PHREEQC replay: OK.
  • Strict Sphinx build: OK.
  • ruff check and format: OK.
  • LF line endings.

Summary line, then Added, Changed, Fixed and Compatibility and limits, with short bullets and issue numbers. The full text of the 31 entries moves unchanged to docs/releases/0.6.0.md, linked from the changelog.
@rafatahmed rafatahmed self-assigned this Oct 23, 2026
The changelog's link to docs/releases/0.6.0.md is a full GitHub URL: the docs site includes CHANGELOG.md, where a relative link does not resolve and the strict build failed. CONTRIBUTING describes the release structure and tests/test_changelog.py enforces it for Unreleased and every release from 0.6.0 on.
@read-the-docs-community
Copy link
Copy Markdown

Documentation build overview

📚 Flahax | 🛠️ Build #35364184 | 📁 Comparing ca701f9 against latest (93966bc)

  🔍 Preview build  

1 file changed
± changelog.html

@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.81%. Comparing base (93966bc) to head (ca701f9).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #153   +/-   ##
=======================================
  Coverage   89.81%   89.81%           
=======================================
  Files          54       54           
  Lines        7367     7367           
=======================================
  Hits         6617     6617           
  Misses        750      750           
Flag Coverage Δ
unittests 89.81% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@rafatahmed
rafatahmed merged commit 3160a9f into main Oct 23, 2026
10 checks passed
@rafatahmed
rafatahmed deleted the docs/changelog-0.6.0 branch October 23, 2026 20:11
@rafatahmed rafatahmed changed the title Structure the 0.6.0 changelog like earlier releases Professional changelog (Keep a Changelog), README, CLI help and troubleshooting Oct 23, 2026
@rafatahmed
Copy link
Copy Markdown
Owner Author

Note: the last commit described above (Keep a Changelog for every release, README, CLI help, troubleshooting) was pushed after this PR was merged, so it did not reach main. It is in a new PR: see the PR from branch docs/professional-docs.

rafatahmed added a commit that referenced this pull request Oct 23, 2026
Professional changelog (Keep a Changelog), README, CLI help and troubleshooting (missed commit of #153)
rafatahmed added a commit that referenced this pull request Nov 7, 2026
Structure the 0.6.0 changelog like earlier releases
rafatahmed added a commit that referenced this pull request Nov 7, 2026
Professional changelog (Keep a Changelog), README, CLI help and troubleshooting (missed commit of #153)
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

0