Post-import next steps tell you to run `gh plate config init` when .plate already exists
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
Research direction
Read the next-steps logic referenced in packaging.py:37, bootstrap.py:160, and adoption.py:103, then locate the post-import report and its unittest coverage. Check the behavior when .plate already exists; done means the report no longer suggests gh plate config init in that case and a unittest verifies it.
Written by the indexing model from the issue text.
Description
Reported by an adopter (Coacharino) after gh plate import-payload --apply on akasper/coacharino.
Repro
- Run
gh plate import-payload --apply. The payload already includes.plate. - Follow the printed next steps, which say to run
gh plate config init(seepackaging.py:37,bootstrap.py:160,adoption.py:103). gh plate config initreports that.platealready exists.
Expected
Next-steps text is conditional. It only suggests gh plate config init when .plate is missing, and otherwise points to the next real step. Add a unittest that a post-import report never suggests config init when .plate exists.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 4d 44m
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from akasper/plate
-
area:security Task
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
area:cli Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
need:refinement status:stub
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 2 days
-
need:refinement status:stub
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Design: a PLATE-native way to close and manage Question issues (Closes fails on release branches)Openarea:cli area:docs Design need:decision
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
521xueweihan/HelloGitHub#4150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
aws-samples/sample-per-model-bedrock#595 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug connectors
Difficulty 1/5 Under an hour Newbie friendliness 67/100
pyinfra-dev/pyinfra#2036 ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day