dereksmart / release-me Goto Github PK

See https://github.com/10up/actions-wordpress/tree/develop/dotorg-plugin-deploy for an example.

When it comes time to tag the release, we should be checking that the version numbers are correct.

The version numbers are in 4 different places:

• Plugin header
• Constant (in main plugin file)
• Readme
• Package.json

as of ed31f8a, we are getting these version numbers stored in their own variables after cloning. Let's do something with these later?

Since it's looking like a strong possibility there will be multiple .custom files, should we standardize naming?

The files will

• Be named the same in both release-me and the plugin (will work in either environment)
• Do various things (some will be executed as a script, others will be files for variables to be called later)
• All be appended with -sample.
• "Live" files (no -sample) will be .gitignored

Maybe a prefix makes sense? quick identifier in either repo. For example, if it's in Jetpack, it could be .jprm-*-sample :

• .jprm-releaseignore-sample
• .jprm-variables-sample
• .jprm-settings-sample
• .jprm-precheck-sample
• etc...

Eventually, it will do many things such as

• Milesone kickoff
• Managing release branches
• Publishing to github & SVN

So what should we call it? Something that will result in a cool acronym would be idea.

• Jetpack Release Manager? jprm
• Jetpack Releaser? jpr
• Something else?

After answering all the prompts, would be cool for confirmation screen to show you what the command would have been if using script args, so that someone can just copy/paste it next time and skip the prompts.

Example of what it could look like during confirmation:

Make the settings over-writable. Kinda like a filter system.

will probably do .custom-sample and instruct to create .custom which will be gitignored and can be a whole gang of variables.

I prefer to have no file extensions only for binaries. For shell scripts I prefer .sh or .bash

Not all plugins need yarn.

Create an override that will execute something like

if exists in .custom, execute that command. It should probably be executed as a script. Actually, it might be simpler if it were it's own *-sample file. cause you could just if exists exec {filename}