I think this is the point where @joemcgill is looking for some sort of output to view what would have been sent across to SVN

@jeffpaul For the unbundling of the Performance Lab plugin, we did a similar thing in which we downloaded the deploy.sh file in our repo and removed this line of code so it would not commit to the SVN repo. Our main intention is that we can check all the processes that the deploy script performs but not commit the files to the SVN repository.

Check WordPress/performance#700 (comment) for more details.

Looking at this again, I think this would actually make more sense as a proper input for the action, like generate-zip. This makes it part of the actual API of the action and less fragile to variance of however someone might use/pass an environment variable. Ultimately it would still be an environment variable in the script, but one that isn't intended to be passed manually.

Then we could follow the same simple conditional style that is used for $INPUT_GENERATE_ZIP

What do you think?

Thanks @aaemnnosttv, for the feedback. Do we need to add dry-run.yml to this PR so others can see how it will be used?

I don't think we would need a new dry-run.yml file. I would suggest updating the action.yml file to set a default for the input

inputs:
  generate-zip:
    description: 'Generate package zip file?'
    default: false
  dry-run:
    description: 'Run the deployment process without committing.'
    default: false

And then set the environment variable based on the input here

      env:
        INPUT_GENERATE_ZIP: ${{ inputs.generate-zip }}
        INPUT_DRY_RUN: ${{ inputs.dry-run }}

Thanks @joemcgill 👍

@mukeshpanchal27 this looks like the only part that's left to do here 🙂