docs: fixed workflow #466
docs: fixed workflow #466
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
.github/workflows/docs.yaml
Outdated
| gh pr create \ | ||
| --body "" \ | ||
| --title "docs: update zed docs" \ | ||
| --head "update-generated-docs" \ | ||
| --base "main" | ||
| else | ||
| echo "No changes detected in $TARGET_DOCS_FILE." | ||
| echo "CHANGES_DETECTED=false" >> $GITHUB_ENV | ||
| fi |
There was a problem hiding this comment.
Have you seen this action? https://github.com/marketplace/actions/create-pull-request
Would it work for this use case? We use it in other actions: https://github.com/authzed/authzed-node/blob/main/.github/workflows/automatic-api-update.yaml#L37-L47
There was a problem hiding this comment.
Yeah did have a look over the documentation, kartikaysaxena/docs#2 was the result of changes, switching to this action.
kartikaysaxena
force-pushed
the
docs/workflow
branch
2 times, most recently
from
d403ce1 to
78bb72b
Compare
Signed-off-by: Kartikay <kartikay_2101ce32@iitp.ac.in>
kartikaysaxena
force-pushed
the
docs/workflow
branch
from
78bb72b to
e21dd45
Compare
tstirrat15
left a comment
tstirrat15
left a comment
There was a problem hiding this comment.
Cool, this looks good!
|
There was a perms failure: https://github.com/authzed/zed/actions/runs/13243163183/job/36963066495 I think there might be something about a PAT or the permissions on the token declared at the top of the file? I'm curious as to why it worked in your fork but not here. |
2 participants
Related #464
Fixed workflow, tested on fork, example PR kartikaysaxena/docs#1
The token should have read/write permissions