actions-marketplace-validations/Publish Raycast Extension
Automatically publish changes to a Raycast extension from your own repo to the central `raycast/extensions` repo
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| raycast_extensions_fork_full_name | The full name of your fork of the `raycast/extensions` repo (for example `timrogers/extensions`) | yes | — |
| github_access_token | A GitHub personal access token with the `repo` and `workflow` permissions, used to push to your fork of `raycast/extensions` (see `raycast_extensions_fork_full_name`) and create pull requests to the `raycast/extensions` repo. For security reasons, you should store this as an [encrypted secret](https://docs.github.com/en/actions/security-guides/encrypted-secrets). | yes | — |
| github_username | The username of the GitHub user that the `github_access_token` belongs to | yes | — |
| extension_name | The name of your extension. This should be lower case, with dashes separating words (e.g. `iata-code-decoder`). If you've already published your extension at least once to the `raycast/extensions` repo, this should be the name of the folder under `extensions/` where your extension lives. | yes | — |
Outputs
| name | description |
|---|---|
| pull_request_url | The URL of the pull request to `raycast/extensions` |