Skip to content

Add validate command #573

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
vimalk78 wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Add validate command #573

vimalk78 wants to merge 2 commits into from

Conversation

@vimalk78
Copy link
Contributor

@vimalk78 vimalk78 commented Sep 19, 2025

Added a command to validate syntax of another command, using existing validation logic.

validate <command> - Check command syntax without executing

requires merging #571

@vimalk78
feat: improve Slack bot UX with robust parsing and progressive help
2f1b0f0 
  - Replace monolithic help with categorized progressive help system
  - Add dedicated help functions for each command category
  - Handle trailing commas/spaces in ParseImageInput without errors
  - Add fuzzy matching with "Did you mean?" suggestions for typos
  - Add comprehensive test coverage for parsing edge cases

Signed-off-by: Vimal Kumar <vimal78@gmail.com>
@vimalk78
feat: add validate command for dry-run testing
62e73a7 
  - Add validate command to check syntax without execution
  - Support validation for launch, test, and build commands
  - Include detailed error messages and configuration preview
  - Update help documentation with validate examples
  - Use existing CheckValidJobConfiguration for validation logic

Signed-off-by: Vimal Kumar <vimal78@gmail.com>
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 19, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vimalk78
Once this PR has been reviewed and has the lgtm label, please assign jupierce for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented Sep 27, 2025

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 27, 2025
@openshift-bot
Copy link

openshift-bot commented Dec 27, 2025

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 27, 2025
@openshift-bot
Copy link

openshift-bot commented Jan 26, 2026

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@vimalk78 @openshift-merge-robot @openshift-bot