Skip to content

Add automated release GitHub Action - #219

Draft
claytoncollie wants to merge 1 commit into
developfrom
feature/automated-release-action
Draft

Add automated release GitHub Action#219
claytoncollie wants to merge 1 commit into
developfrom
feature/automated-release-action

Conversation

@claytoncollie

@claytoncollie claytoncollie commented Feb 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds a GitHub Actions workflow (.github/workflows/release.yml) that automates the release process when a v* tag is pushed
  • Creates a .distignore file to exclude dev-only files from the release ZIP
  • Documents the release process in README.md

The workflow builds assets, installs production Composer dependencies, packages a clean ZIP using rsync --exclude-from=.distignore, and creates a GitHub release with the artifact attached. Supports workflow_dispatch for manual triggers.

Closes #197

Test plan

  • Push a test tag (e.g. v0.0.0-test) to verify the workflow runs successfully
  • Confirm the generated ZIP contains only production files (no node_modules, .github, linting configs, etc.)
  • Confirm the ZIP has the correct 10up-experience/ directory structure for WordPress installation
  • Verify the GitHub release is created with auto-generated release notes and the ZIP attached
  • Test workflow_dispatch manual trigger from the Actions tab

Introduces a GitHub Actions workflow triggered by version tags (v*) that
builds assets, packages a clean ZIP via .distignore, and creates a GitHub
release with the artifact attached. Adds release process documentation
to README.

Closes #197

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@claytoncollie claytoncollie self-assigned this Feb 27, 2026
@jeffpaul jeffpaul added this to the 1.20.0 milestone Aug 12, 2026
@jeffpaul
jeffpaul requested a lite review from Copilot August 12, 2026 15:21

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Adds an automated GitHub Actions-based release pipeline so tagged versions can be built and published as GitHub Releases with a packaged ZIP suitable for WordPress installation.

Changes:

  • Adds a release.yml workflow that triggers on v* tags (and supports manual workflow_dispatch) to build assets, install production dependencies, ZIP the plugin, and create a GitHub Release.
  • Introduces .distignore to control which files are excluded from the packaged release directory/ZIP.
  • Documents the release/tagging process in README.md.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
README.md Documents the new automated release/tagging workflow for maintainers.
.github/workflows/release.yml Implements the automated build/package/release GitHub Action.
.distignore Defines exclusions used during packaging to produce a clean release ZIP.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread .distignore
Comment on lines +1 to +3
/.github
/.husky
/node_modules
Comment thread README.md
```
3. **Automation handles the rest:** The GitHub Action installs dependencies, builds assets, packages a clean ZIP (excluding dev files via `.distignore`), and creates a GitHub release with auto-generated release notes.

The workflow can also be triggered manually from the Actions tab using `workflow_dispatch` for dry runs or re-releases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add automated release GitHub Action with README documentation

3 participants