[FEATURE] Exec to return exit code 1 on error

Open
#60 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

Start at the stackql exec command entry point and trace how errors are returned. Identify the relevant error paths and verify that each encountered error produces exit code 1, including the CI/CD use case; the issue names no files or tests to run.

Written by the indexing model from the issue text.

Description

enhancement v0.4

Feature Description

stackql exec... should return exit code 1 where an error is encountered. This is useful for CICD, and doubtless other things.

Example(s)
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Possible Approaches or Libraries to Consider
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Dominant language
Go
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackql/stackql-devel

All issues in stackql/stackql-devel

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.