Skip to content

docs(readme): keep the overview free of release history - #50

Merged
fadwen merged 1 commit into
mainfrom
docs/readme-cleanup
Oct 19, 2026
Merged

fadwen merged 1 commit into
mainfrom
docs/readme-cleanup

Conversation

@fadwen

@fadwen fadwen commented Oct 19, 2026

Copy link
Copy Markdown
Owner

Summary

The README is the overview a first-time visitor reads, and it carried the module's release history in its margins: nineteen section headings ended in the version that introduced the feature, such as "Suppressions and settings (0.13)", the tenant pre-flight paragraph said since when each check existed, and the roadmap listed thirteen features by version. None of that helps someone deciding whether the module does what they need, and all of it is in CHANGELOG.md. The changelog's own preamble linked to the private repository the module was first developed in, which a visitor cannot open.

Changes

  • README.md: the "(0.x)" suffix is gone from every heading; "since 0.17" and "Since 0.21" are gone from the tenant pre-flight paragraph; the roadmap bullet says everything on the original list has shipped and points at the changelog for when.
  • CHANGELOG.md: the preamble says versions before 0.25.0 came from a private repository, without the link or the path; a Changed entry under Unreleased records the cleanup.

Verification

  • No (0.x) heading suffix or "since 0.x" phrase remains in README.md; the Markdown structure (headings, lists, tables, code fences) is unchanged apart from the removed suffixes and the shorter roadmap bullet.
  • No test or build step reads these passages: Build/Publish-Module.ps1 ships the README as is, and the one test that mentions the README cites it in a comment.
  • Prose only; no code, help or workflow changed.

Nineteen section headings ended in the version that introduced the
feature, the tenant pre-flight paragraph said since when each check
existed, and the roadmap listed thirteen features by version. A first
visitor wants the overview; the history is in CHANGELOG.md, which the
roadmap now points at. The changelog's preamble no longer links to the
private repository the module was first developed in.

@fadwen fadwen left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Notes on the lines whose reason the diff does not show.

Comment thread README.md
(0.13), SARIF (0.14), Repair-IntuneScript (0.15), filters (0.17), another account (0.18), the
Enrollment Status Page (0.19), drift (0.20), assignment sanity (0.21), the health report (0.22),
timelines and the diagnostic zip (0.23). See [CHANGELOG.md](CHANGELOG.md).
has shipped; [CHANGELOG.md](CHANGELOG.md) says what arrived when.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

The roadmap keeps its one bullet, 1.0, because that is the only forward-looking statement the README makes; the thirteen shipped items were history dressed as a plan, and the changelog carries them with dates.

Comment thread CHANGELOG.md
[powershell_scripts](https://github.com/fadwen/powershell_scripts) repository, where the module
lived under `Scripts/Intune/IntuneScriptLab`. Their entries are carried over from the manifest's
release notes.
Versions before 0.25.0 were released from a private repository where the module began; their

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

The sentence stays so the version numbers below 0.25.0 have an explanation, since their entries have no commits in this repository to point at; only the link and the path went, because a visitor cannot open the private repository and the path inside it tells them nothing.

@fadwen
fadwen merged commit bcd2dab into main Oct 19, 2026
4 checks passed
@fadwen
fadwen deleted the docs/readme-cleanup branch October 19, 2026 18:06
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