action-wordpress-plugin-deploy icon indicating copy to clipboard operation
action-wordpress-plugin-deploy copied to clipboard

How can I run it in a subfolder?

Open 0xBeycan opened this issue 1 year ago • 1 comments
trafficstars

For example, I have a repository like below.

folder free-plugin folder: pro-plugin folder. tests etc, etc

when this step works I want to send only the ones under free-plugin but if I add BUILD_DIR .distignore doesn't work and it doesn't send the .wordpress-org folder i.e. assets.

How can I do this?

0xBeycan avatar Oct 04 '24 07:10 0xBeycan

Also, when I create releases, I give tag names as “x.x.x.x-free” and “x.x.x-pro” so that I can run the job I want in the action. However, although I give the “VERSION” value to your action, it still creates a folder under tags as “x.x.x.x-free”.

0xBeycan avatar Oct 04 '24 07:10 0xBeycan

Hi @0xBeycan,

Thanks for the opening the issue and apologies for the delay response on this.

when this step works I want to send only the ones under free-plugin but if I add BUILD_DIR .distignore doesn't work and it doesn't send the .wordpress-org folder i.e. assets.

Yes, that it expected. As it is expected that BUILD_DIR is contains only built files, .distignore don't work there. However, Could you please provide more information on the folder structure and where your config files, assets etc...? Also, have you tried running action into that specific directory using working-directory (docs)?

Thanks!

iamdharmesh avatar Aug 21 '25 13:08 iamdharmesh

Hi, I figured it out. .distignore is working when in the main folder.

0xBeycan avatar Aug 22 '25 00:08 0xBeycan

It has been 7 days since more information was requested from you in this issue and we have not heard back. This issue is now marked as stale and will be closed in 7 days, but if you have more information to add then please comment and the issue will stay open.

github-actions[bot] avatar Aug 29 '25 02:08 github-actions[bot]

This issue has been automatically closed because there has been no response to our request for more information. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. See this blog post on bug reports and the importance of repro steps for more information about the kind of information that may be helpful.

github-actions[bot] avatar Sep 06 '25 02:09 github-actions[bot]