Send test post to verify that the automation works #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc @nodejs/tsc (sorry for the noise, I guess there's trial and error for everything for the first time! But the validation workflow looks happy enough ;)) |
anonrig
approved these changes
Dec 1, 2024
|
🚀 |
|
For posterity, it works: https://bsky.app/profile/nodejs.org/post/3lcd5ct56w42m |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reopened from #5 from a branch in this repository, because turns out secrets are not available to workflows started from forks (duh). Will do a bit of follow-up to split the validation into full validation (validates bluesky URL references which requires secrets) + local validation (just that the JSON looks right, without requiring secrets) as mentioned in #5 (comment) but for now creating PRs from branches in this repo should be fine.