Docs/friction: consumers pinning main cannot reproduce a revision deterministically

Open Beginner friendly
#180 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
git
Domain
documentation

Research direction

Start with the README installation section and inspect the existing VERSION and plugin.json contract. Check the repository’s release-please tags and document how submodule or plugin-style consumers can pin a release tag instead of main. Done means the guidance covers deterministic tag-based pinning and the VERSION/plugin.json relationship.

Written by the indexing model from the issue text.

Description

We vendor conductor into our repo via submodule pinned to main HEAD (f06add3 at time of registration).

Observation: release-please tags exist in this repository but there is no documented guidance for consumers to pin a release tag instead of floating main. Floating-main pins work today, but they make compliance receipts harder: we record exact SHAs per bump and re-review each advancement.

Suggestion: mention tag-based pinning (and the VERSION/plugin.json contract) in the README installation section for submodule/plugin-style consumers.

Dominant language
Python
Stars
3.7k
Forks
295
Avg merge
9m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gemini-cli-extensions/conductor

All issues in gemini-cli-extensions/conductor

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.