Skip to content

README/docstring convention cleanup - #55

Merged
andremun merged 2 commits into
masterfrom
docs/readme-remove-internal-notes
Aug 22, 2026
Merged

README/docstring convention cleanup#55
andremun merged 2 commits into
masterfrom
docs/readme-remove-internal-notes

Conversation

@andremun

@andremun andremun commented Aug 22, 2026

Copy link
Copy Markdown
Owner

Summary

Two rounds of documentation-convention cleanup, both docs-only:

  1. README.md had accumulated a few spots narrating how something got to its current state (a CI confirmation, an issue number, a prior implementation detail, an internal spec-section reference) rather than just stating the current user-facing fact. Removed those, and dropped the Communications Toolbox mention entirely (a toolbox that isn't used doesn't need a line explaining that).
  2. A repo-wide docstring/doc-convention audit turned up three more inconsistencies, now fixed:
    • README.md's ~208 inline code spans used triple backticks instead of the single-backtick convention every other doc (CONTRIBUTING.md, SECURITY.md, CLAUDE.md, RELEASE_NOTES.md) already uses. Converted, leaving the genuine fenced code blocks untouched.
    • core/PYTHIA.m was the one core/ pipeline file still documented as free narrative prose instead of the structured Inputs/Outputs section its siblings (PRELIM, SIFTED, PILOT, CLOISTER, TRACE, FILTER, INIT) all have. Added.
    • A few internal section-divider comment lines in output/scriptpng.m and example.m used 69/71 dashes instead of the 73-dash width used everywhere else. Normalized.

liveDemoIS.m's citation (in prose before its license header rather than in the standard % Reference: block) was checked and left as-is, by request.

No code behaviour changes anywhere in this PR.

Test plan

  • N/A (docs/docstrings only).

Three spots described how the file/toolkit got to its current state
(CI confirmation, an issue number, a prior implementation detail, an
internal spec section reference) rather than just the current
user-facing fact. Also drops the Communications Toolbox mention
entirely (a toolbox that isn't used doesn't need a line explaining
that).
Copilot AI lite review requested due to automatic review settings August 22, 2026 05:33

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

- README.md: convert ~208 inline code spans from triple backticks to
  standard single backticks, matching CONTRIBUTING.md/SECURITY.md/
  CLAUDE.md/RELEASE_NOTES.md's convention. Fenced code blocks (the
  repository-layout tree, MATLAB examples) untouched.
- core/PYTHIA.m: add the structured Inputs/Outputs docstring section
  its core/ siblings (PRELIM, SIFTED, PILOT, CLOISTER, TRACE, FILTER,
  INIT) all have; it was the one core pipeline file still documented
  as free narrative prose instead.
- output/scriptpng.m, example.m: normalize internal section-divider
  comment lines to the same 73-dash width used everywhere else (some
  were 69 or 71 dashes).

liveDemoIS.m's inline (pre-header) citation is left as-is, by request.
@andremun andremun changed the title README: remove internal development-process narration README/docstring convention cleanup Aug 22, 2026
@andremun
andremun merged commit b1931c8 into master Aug 22, 2026
2 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.

3 participants