ci: add workflow to automate the release PR to zed-industries/extensions#160
ci: add workflow to automate the release PR to zed-industries/extensions#160mrm007 wants to merge 5 commits intobiomejs:mainfrom
Conversation
|
So, if I understand correctly, we need a fork of Should we have a fork in the If that's the creator of the github action, it doesn't feel right |
|
@ematipico The owner of the There are many Zed extensions using the GitHub action, e.g. joshuadavidthomas/zed-django#10 and the result zed-industries/extensions#3691. I made the action runnable with any fork for convenience. But after reviewing the code it seems like the |
| inputs: | ||
| forked_repo: | ||
| description: "The forked repository of the zed-industries/extensions repo e.g. mrm007/extensions" | ||
| required: true | ||
| type: string |
There was a problem hiding this comment.
| inputs: | |
| forked_repo: | |
| description: "The forked repository of the zed-industries/extensions repo e.g. mrm007/extensions" | |
| required: true | |
| type: string |
Remove once the biomejs/zed-extensions repo is created (name pending).
| with: | ||
| extension-name: biome-zed | ||
| # extension-path: extensions/${{ extension-name }} | ||
| push-to: ${{ inputs.forked_repo }} |
There was a problem hiding this comment.
| push-to: ${{ inputs.forked_repo }} | |
| push-to: biomejs/zed-extensions |
Update once the biomejs/zed-extensions repo is created (name pending).
Fixes #157.
I have combined the instructions from the GitHub Action with workflow inputs so the release can be deployed from any fork, without manually changing the workflow every time.
A
COMMITTER_TOKENpersonal access token needs to be created with "repo" & "workflow" scopes.This is what running the action will look like: