Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
1 change: 1 addition & 0 deletions .github/workflows/end-to-end.yml
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,7 @@ jobs:
configure-flags: '--with-hello-name=FROM_MY_ACTION --enable-example-pie-extension'
release-tag: ${{ env.RELEASE_TAG }}
github-token: ${{ secrets.GITHUB_TOKEN }}
upload-artifacts: 'true'

- name: Check Output
run: |
Expand Down
14 changes: 8 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ them to your GitHub releases. It will:
- Build a `.so` from your extension
- Package the `.so` in an archive, and name it according to PIE's expectations
- Upload the archive to your GitHub release
- Optionally upload the archive as a workflow build artifact

> [!TIP]
> Looking for Windows support? You probably want [`php/php-windows-builder`](https://github.com/php/php-windows-builder?tab=readme-ov-file#examples)
Expand All @@ -30,12 +31,13 @@ with:

### Inputs

| Name | Description | Required | Default |
|-------------------|-------------------------------------------------------------------------------------------------|----------|---------|
| `release-tag` | The tag to use when building the extension; there must be an existing draft release for the tag | `true` | - |
| `github-token` | The GitHub token to use. Usually `${{ secrets.GITHUB_TOKEN }}` would be fine for most cases. | `true` | - |
| `configure-flags` | If you need to pass additional flags to the `./configure` command, specify them here | `false` | `''` |
| `build-path` | Path to the extension source directory containing `config.m4`, relative to repo root | `false` | `'.'` |
| Name | Description | Required | Default |
|--------------------|-------------------------------------------------------------------------------------------------|----------|-----------|
| `release-tag` | The tag to use when building the extension; there must be an existing draft release for the tag | `true` | - |
| `github-token` | The GitHub token to use. Usually `${{ secrets.GITHUB_TOKEN }}` would be fine for most cases. | `true` | - |
| `configure-flags` | If you need to pass additional flags to the `./configure` command, specify them here | `false` | `''` |
| `build-path` | Path to the extension source directory containing `config.m4`, relative to repo root | `false` | `'.'` |
| `upload-artifacts` | Whether to upload the generated `.zip` as a workflow build artifact | `false` | `'false'` |

### Outputs

Expand Down
4 changes: 4 additions & 0 deletions action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,10 @@ inputs:
description: 'Path to the extension source directory containing config.m4 (relative to repo root)'
required: false
default: '.'
upload-artifacts:
description: 'Whether to upload the generated .zip as a workflow build artifact'
required: false
default: 'false'
release-tag:
description: 'The tag to use for the release'
required: true
Expand Down
Loading