Repository navigation
Add vapour publish workflow with required flags - #1
Closed
madhavkhoslaa wants to merge 1 commit into
Closed
madhavkhoslaa wants to merge 1 commit into
madhavkhoslaa wants to merge 1 commit into
Conversation
Author
|
Closing this PR per review: it targets the wrong base () and its workflow writes build output into . Replaced by a new PR from that keeps /assets Cargo.lock flake.lock LICENSE README.md |
Author
|
Follow-up note: this was closed because it targeted |
This file contains hidden or 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
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.
Summary
.github/workflows/vapour-publish.ymlthat builds web output and callsvapour-computer/vapour-ci@v1versionfrom tag name with leadingvstrippednotestextWhy
Requested in PUBLISH-FLAGS-TASK so the tutorial repo has a publish workflow compatible with required publish flags.
Drafted with opencode (openai/gpt-5.3-codex).