Skip to content

Test release action with deployment #12 #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
IgorCode merged 1 commit into from
Nov 11, 2025
Merged

Test release action with deployment #12 #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
name: Deploy to WordPress.org Repository

on:
release:
types: [released]

jobs:
deploy:
name: Deploy to WP.org
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v5

# # Optional: If your plugin is using composer dependencies, we want to include them
# # WITHOUT the dev dependencies.
# - name: Build
# run: |
# npm install
# npm run build
Comment on lines +15 to +20
Copy link

Copilot AI Nov 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comment is misleading. The commented build step runs npm commands, not composer. The project does have composer dev dependencies (phpstan) that should be excluded from production builds. Consider either removing this comment or updating it to accurately reflect that it's for npm/build assets, and add a separate step for composer production dependencies if needed using composer install --no-dev.

Suggested change
# # Optional: If your plugin is using composer dependencies, we want to include them
# # WITHOUT the dev dependencies.
# - name: Build
# run: |
# npm install
# npm run build
# # Optional: If your plugin is using npm (Node.js) build assets, run the build here.
# - name: Build assets
# run: |
# npm install
# npm run build
#
# # Optional: If your plugin is using composer dependencies, install them WITHOUT the dev dependencies.
# - name: Install Composer production dependencies
# run: composer install --no-dev --optimize-autoloader

Copilot uses AI. Check for mistakes.

- name: WordPress Plugin Deploy
id: deploy
uses: 10up/action-wordpress-plugin-deploy@stable
with:
generate-zip: true
dry-run: true
Copy link

Copilot AI Nov 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dry-run: true flag means this workflow will not actually deploy to WordPress.org. For a production release workflow, this should be set to false. If this is intentional for testing purposes, consider adding a comment explaining why dry-run is enabled.

Suggested change
dry-run: true
dry-run: false

Copilot uses AI. Check for mistakes.
env:
SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}

# After the deploy, we also want to create a zip and upload it to the release on GitHub. We don't want
# users to have to go to the repository to find our plugin :).
- name: Upload release asset
uses: softprops/action-gh-release@v2
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
files: ${{ github.workspace }}/${{ github.event.repository.name }}.zip