[WIP] RHDEVDOCS-6146: Update Condition management commands section to follow correct style

[Maharshi-Project]

Version(s): pipelines-docs-1.14, pipelines-docs-1.15, pipelines-docs-1.16

Issue: https://issues.redhat.com/browse/RHDEVDOCS-6146

Link to docs preview: https://82210--ocpdocs-pr.netlify.app/openshift-pipelines/latest/tkn_cli/op-tkn-reference.html

QE review:

• QE has approved this change.

Additional information:
Updated the document according to RHDEVDOCS-6146

[openshift-ci-robot]

@Maharshi-Project: This pull request references RHDEVDOCS-6146 which is a valid jira issue.

In response to this:

Version(s): pipelines-docs-1.14, pipelines-docs-1.15, pipelines-docs-1.16

Issue: https://issues.redhat.com/browse/RHDEVDOCS-6146

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:
Updated the document according to RHDEVDOCS-6146

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @Maharshi-Project. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[Maharshi-Project]

@eromanova97
Can you please review this PR ?

[openshift-ci]

@Maharshi-Project: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

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.

[Srivaralakshmi]

/ok-to-test

[ocpdocs-previewbot]

🤖 Wed Sep 25 13:22:22 - Prow CI generated the docs preview:

https://82210--ocpdocs-pr.netlify.app/openshift-pipelines/latest/tkn_cli/op-tkn-reference.html

[openshift-ci-robot]

@Maharshi-Project: This pull request references RHDEVDOCS-6146 which is a valid jira issue.

In response to this:

Version(s): pipelines-docs-1.14, pipelines-docs-1.15, pipelines-docs-1.16

Issue: https://issues.redhat.com/browse/RHDEVDOCS-6146

Link to docs preview: https://82210--ocpdocs-pr.netlify.app/openshift-pipelines/latest/tkn_cli/op-tkn-reference.html

QE review:

• QE has approved this change.

Additional information:
Updated the document according to RHDEVDOCS-6146

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 openshift-eng/jira-lifecycle-plugin repository.

[eromanova97]

/ok-to-test
/lgtm

[Srivaralakshmi]

/lgtm

[Srivaralakshmi]

Hello @Maharshi-Project: I see 9 commits now. There seems to be some issue with rebasing (syncing) with the pipelines-docs-main branch, which caused multiple commits and changes appearing in your PR.

It is difficult to help with this fix from distance, but I will try my best. You can try these steps to fix it:

$ git checkout <your_feature_branch> #(for example, git checkout feature-pipeline-docs-main)
$ git fetch upstream
$ git rebase upstream/pipelines-docs-main
$ git push -f origin <your_feature_branch> #(for example, git push -f origin feature-pipeline-docs-main)

If something goes wrong (you'll see some merge conflicts when you run the git rebase upstream/pipelines-docs-main command), then the easier option is to update your local repository and start your PR from scratch:

$ git checkout pipelines-docs-main
$ git fetch upstream
$ git rebase upstream/pipelines-docs-main
$ git push origin pipelines-docs-main
$ git checkout -b <new_feature_branch>

And make changes again on the new up-to-date feature branch 🙂 Thank you!

[openshift-ci]

@Maharshi-Project: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/validate-portal	6dc45bc	link	true	/test validate-portal
ci/prow/validate-asciidoc	6dc45bc	link	true	/test validate-asciidoc

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.