Restructure repo into plugin-name directory layout for Pi Agent installs #1
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
weisanju/pi-plugins!1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "copilot/optimize-directory-structure"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This update aligns the repository with a plugin-first structure: each plugin now lives under a top-level directory named after the plugin, and root docs reflect the
pi-pluginsnaming/direction. The goal is to make Pi Agent installation and future multi-plugin expansion straightforward.Repository structure
pi-model-auto-router/.Root-level project documentation
README.mdthat defines the new convention: one top-level folder per plugin, named by plugin.Install/discovery convention for future plugins