`gh plate health` adoption_next_command prints literal OWNER/REPO

Open
#1,190 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@akasper is already working on this.

Since Nov 1, 2026.

  • #1318 by @akasper — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
cli

Research direction

Start with adoption.py around line 203 and import_payload.py around line 297, where adoption_next_command prints the command. Trace how --repo, .plate, and the git origin remote are resolved, then find the related unittest coverage. Done means the command uses the resolved owner/repo, explains when it must fall back to the placeholder, and tests both paths.

Written by the indexing model from the issue text.

Description

area:cli Bug

Reported by an adopter (Coacharino) on akasper/coacharino.

Repro

Run gh plate health --json (or gh plate import-payload --apply) in an adopted repo with core checks failing. adoption_next_command prints the literal gh plate bootstrap --repo OWNER/REPO --adopt --apply, which comes from adoption.py:203 and import_payload.py:297.

Expected

Fill in the real owner/repo, taken from --repo, .plate, or the git origin remote. Fall back to the placeholder only when none of these resolve, and say so. Add unittest coverage for both paths.

Dominant language
Python
Stars
1
Forks
0
Avg merge
1d 23h
Merged PRs (30d)
49

Getting set up

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 akasper/plate

All issues in akasper/plate

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.