Plugin CLI - Githubissues

philpax commented 2 years ago

There are a few workflows that come up reasonably often during plugin development and publishing. We could offer an optional CLI to assist with these.

Initial thoughts:

Automatically updating the manifest with particular details (author, version). Potentially the csproj if #17 goes ahead with moving the manifest to the csproj.
- dmp edit version 1.1.0
Building a single package that can be directly loaded into Dalamud, so that you can send testing plugins
- dmp build-test-package
Automatically making a PR to submit an update using the current remote + commit
- dmp submit --location plugin --changelog "Tightened up the graphics on Level 3"

I'm sure there are more, just getting this issue down for reference

karashiiro commented 2 years ago

dmp makes me think dumpy; what's it actually supposed to stand for?

philpax commented 2 years ago

Was honestly just the first thing that came to mind for "DalaMud Plugin", but there are definitely better options! This is more for @kalilistic to share their thoughts on.

avafloww commented 2 years ago

I know it's the funny joke, but I will unironically suggest plogon as the CLI tool name.

karashiiro commented 2 years ago

When we're writing CI scripts, we'll need to use where plogon to ensure that the CLI is installed.

philpax commented 2 years ago

Is this still necessary with the implementation of DIP17 + the eventual implementation of https://github.com/goatcorp/Dalamud/issues/961?

goatcorp / DIPs

Plugin CLI #26