Skip to content

docs: add set-requirements to setup header and cite #12/#9 in [0.1.1] #16

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

Closed
clawgenti wants to merge 1 commit into from
Closed

docs: add set-requirements to setup header and cite #12/#9 in [0.1.1] #16

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 2 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,8 @@ to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

### 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 5, 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: these are the first PR citations in this file — every other bullet, including the Shellcheck one two lines below, has none, so the section becomes inconsistent. If the intent is traceability, cite every entry and link it Keep-a-Changelog style (([#12](https://github.com/rossoctl/repoman/pull/12))); a bare #12 is plain text in Markdown, not a link. Otherwise drop both cites and keep the body uniform.

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

@jimcadden jimcadden Nov 5, 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: the banner is narrower than "interactive sessions" — skills/repoman/SKILL.md § Startup banner says to print it "On a human /repoman turn" and to skip it on 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
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
# 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