what next
i have been hacked some times ago that disarranged and disorganized all my system so i need a single working space for myself only now, either in my device system or in my internet services in any other ways, also a strongroom protections for all my works and accounts and make it invisible and impossible for hackers and trackers from having access over my system no matter how greate the hacker system is, also make their command trigger back to them without touching my sytem.905Views0likes0CommentsCode Collab command to move reviews to Inspection state
Hi, I am looking for command to move review to Inspection state. I am able to find command to move state toANNOTATION state, but no luck with the INSPECTION state. Please let me know if there is such command available. Thanks in advance. https://support.smartbear.com/collaborator/docs/reference/command-line/ccollab-admin-review-annotate.html1.3KViews0likes2CommentsHow to send Indicator and/or Log.Message to Console during TestComplete run from command line?
I run TestComplete project from the command line using a .bat file. I would like the Indicator messages or the Log.Message/Error/Warning/Checkpoint or both to appear in the console window during the run of TestComplete from the command line. How can I do this? Thank you.727Views0likes1CommentMatch addgitdiffs commit hash specification in the Command-line client to git commit hash specificat
The addgitdiffs command uses Git commit hash syntax identical to the git tool itself except in one regard: specifying individual commit hashes for addgitdiffs is handled the opposite of how the git tool does it. In Git syntax the following lines are identical: git diff AAAAAAA..BBBBBBB git diff AAAAAAA BBBBBBB In the Collaborator command-line client the following lines have exactly opposite meanings: ccollab addgitdiffs ask AAAAAAA..BBBBBBB ccollab addgitdiffs ask AAAAAAA BBBBBBB This seems to be because the addgitdiffs command handles the second case as a list of individual commits, which it assumes are in reverse chronological order (newest to oldest), rather than a direct pass-thru to the git tool (oldest-first) like the first command. To resolve this, split the addgitdiffs command for specifying a list of commits into a separate command (or require extra options).3KViews0likes0Comments