feat: add task ci to Pulse Taskfile - #2
Merged
Merged
Conversation
Chains fmt, lint, test, and build in sequence so a single `task ci` mirrors what CI should run, failing fast on the first broken step.
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
1 participant
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
task cicommand that chains the existingfmt,lint,test, andbuildaggregate tasks in order.fmt,lint,test,build) was already individually invokable;cijust composes them.cmdsbehavior stops execution on the first non-zero exit, sotask cifails fast and returns a non-zero exit code.Test plan
task --list-allshows the newcitasktask ci --dryconfirms execution order: fmt → lint → test → buildtask: <name>chaining pattern — a failing middle step aborts the run before the next step and exits non-zerotask cirun in an environment with go/cargo/npm/golangci-lint installed (not available in this sandbox)