akasper / akasper/plate

[Task]: Publish public Copilot CLI marketplace entry for PLATE

Open
#381 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Task
Dominant language
Python
Stars
1
Forks
0
Avg merge
8m
Merged PRs (30d)
3

Description

Epic milestone: Post-release marketplace publication

Human action required

Execute the human-owned publication step that makes the PLATE marketplace entry/repository path available as the supported public install channel for Copilot CLI users.

Why the agent cannot safely proceed

The final publication/distribution step may involve human judgment about public visibility, release timing, communications, repository ownership, or account-level settings that should remain under human control.

Context and affected artifacts

  • Epic #384
  • The released PLATE marketplace install surface on the default branch
  • Public GitHub repository marketplace path for Copilot CLI plugins

Best-effort instructions / next steps

  1. Wait until the release containing the marketplace install-surface feature work is cut.
  2. Confirm the repository marketplace artifacts and install docs are public and final.
  3. Perform the human-owned publication or visibility step for the marketplace path.
  4. Validate that intended users can follow the documented public installation flow.
  5. Leave a completion comment without secrets once the publication step is complete.

Done signal

The public marketplace/repository installation path is intentionally published by a human owner, the documented install flow is the supported public path, and the Task issue is closed with a completion comment containing <!-- PLATE-TASK-CLOSED -->.

Related links

  • Epic #384

  • Released marketplace install-surface PR / release artifact

  • This Task will close with a completion comment that includes <!-- PLATE-TASK-CLOSED -->.

  • The completion comment will not include secrets, credentials, tokens, or privileged configuration values.

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.

Research direction

Start by reading Epic #384 and confirming that the released marketplace install-surface artifact, repository marketplace path, and installation documentation are public and final. Perform the human-owned publication or visibility step, validate the documented public installation flow, and close the issue with a completion comment containing <!-- PLATE-TASK-CLOSED -->.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.