Skip to content

docs: combine doc-drift fixes from #14, #15, #16 #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jimcadden merged 3 commits into from
Nov 9, 2026
Merged

docs: combine doc-drift fixes from #14, #15, #16 #22

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ec75e73
docs: fix release 0.1.1 date is 2026-11-05
clawgenti Nov 9, 2026
9d77476
docs: fix release 0.1.0 date is 2026-10-27
clawgenti Nov 9, 2026
0cb4c23
docs: doc-drift updates
clawgenti Nov 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,19 +4,20 @@ All notable changes to this project are documented here. The format is based on
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres
to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [0.1.1] - 2026-11-04
## [0.1.1] - 2026-11-05

### Added

- **doc-drift program.** The scanner and fixer compare documentation to the code at a pinned git ref (paths, flags, enumerations, retired names, versions, and absence claims) and draft Keep a Changelog notes from merged pull requests. It ships inside the `repoman` plugin and as its own marketplace plugin.
- **doc-drift program.** The scanner and fixer compare documentation to the code at a pinned git ref (paths, flags, enumerations, retired names, versions, and absence claims) and draft Keep a Changelog notes from merged pull requests. It ships inside the `repoman` plugin and as its own marketplace plugin. (#12)

@jimcadden jimcadden Nov 9, 2026

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.

suggestion (also from #16): these are the first PR citations in the file — the Shellcheck bullet two lines below has none — so the section is now inconsistent. Either cite every entry and make them links (([#12](https://github.com/rossoctl/repoman/pull/12)); a bare #12 is plain text in Markdown), or cite none and keep the body uniform.

- **REPOMAN banner** on interactive sessions. (#9)

@jimcadden jimcadden Nov 9, 2026

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.

nit (re-raised from #16): "interactive sessions" is broader than what the banner actually does — skills/repoman/SKILL.md § Startup banner prints it on a human /repoman turn and skips schedule/cron, headless -p, pipeline and CI runs. Suggest - **REPOMAN banner** on human /repoman turns. (#9).

- **Shellcheck** for the vendor tooling (`scripts/vendor-engine.sh` and `tests/test-vendor-engine.sh`).

### Changed

- Marketplace version is `0.1.1`. The `v0.1.1` tag is cut from `main` after this release merges.
- Bundled engine is vendored from `rossoctl/automation` `fa619090`, including the pinned-SHA footer for PR review and the weekly report.

## [0.1.0] - 2026-10-23
## [0.1.0] - 2026-10-27

First tagged release of RepoMan, distributed through the `rossoctl-repoman`
marketplace.
Expand Down
8 changes: 4 additions & 4 deletions skills/repoman/scripts/repoman-setup.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
#!/usr/bin/env bash
# Pure writer/validator for the three ~/.repoman file kinds RepoMan reads.
#
# Subcommands: init-config, add-repo, enable-program, set-output. Each writes
# exactly one thing, validates it, and persists atomically (temp file in the
# target directory, then `mv` into place, so a crash mid-write never leaves a
# half-written JSON file).
# Subcommands: init-config, add-repo, enable-program, set-output,
# set-requirements. Each writes exactly one thing, validates it, and persists

@jimcadden jimcadden Nov 9, 2026

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.

suggestion: this file is in the vendor manifest (_vendor.json lists repoman-setup.sh, source rossoctl/automation@fa619090), so the header now diverges from upstream — and upstream still has the old four-subcommand text at both fa61909 and current main (f509e7a). A future scripts/vendor-engine.sh run will silently revert this fix, the same way enable-program --help keeps coming back.

The change itself is correct and matches skills/repoman/SKILL.md:34. Suggest landing the same one-line header edit in rossoctl/automation/scripts/repoman-setup.sh so it survives the next re-vendor.

# atomically (temp file in the target directory, then `mv` into place, so a
# crash mid-write never leaves a half-written JSON file).
#
# This script never calls gh, never prompts, never clones, never forks. It
# receives already-resolved inputs (from the repoman-setup skill) and writes
Expand Down
Loading