gemini-cli-extensions / gemini-cli-extensions/conductor
Docs/friction: consumers pinning main cannot reproduce a revision deterministically
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- git
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100