Add Git commits fails with 'partial entry'
I've been struggling to find a way to add individual Git commits by hash #, both from the GUI and the cli tool. Both of them return the cryptic error "partial entry". Here's the command I'm attempting: ccollab --debug addchangelist 49745 8fe9ef797a1ad4f42f96bccd23ea01243faf918d Here is the stack trace from the CLI tool: FINE: Error running command addchangelist com.smartbear.cmdline.ScmCommunicationException: partial entry at com.smartbear.scm.impl.git.GitLogCmd.handleStdOut(GitLogCmd.java:238) at com.smartbear.scm.cmd.impl.ScmTextCmdAdapter.handleStdOut(ScmTextCmdAdapter.java:32) at com.smartbear.scm.cmd.impl.DebugCommandRunner$DebugCmdWrapper.handleStdOut(DebugCommandRunner.java:181) at com.smartbear.scm.cmd.impl.CommandRunner$2.run(CommandRunner.java:151) at com.smartbear.scm.cmd.impl.CommandRunner$2.run(CommandRunner.java:148) at com.smartbear.scm.cmd.impl.CommandRunner$StreamHandler.call(CommandRunner.java:225) at com.smartbear.scm.cmd.impl.CommandRunner$StreamHandler.call(CommandRunner.java:215) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750) I've attached the log file from running with the --debug flag.
Use collaborator with GitHub WITHOUT webhooks?
Hi, is it possible to use Collaborator with GitHub but without relying on webhooks? For networking reasons, we can't. I see that Collaborator supports "auto-polling" but the docs indicate that's only to discover the existence of new repositories, not to check for updates on existing repositories. True? Barring this, would it be possible to configure it as a plain old git SCM instead of GitHub? In this case, would polling work? And what functionality would be lost? Thanks for the guidance here.
Add multiple pull requests to "Remote System Links"
Currently a pull request from Bitbucket can only be added to the Remote System Links section automatically when the pull request is created, and there isn't a way to add a link to a pull request manually. Is it possible to make an update that allows linking of more than one pull request in a single review? In the case of making small related changes across multiple repositories, it would be very beneficial to be able to include more than one pull request in a single review, to allow those changes to be reviewed as a set.Implement sync of GitHub pull request reviewers and Collaborator reviewers
Submitted on behalf of Debdas Mondal (HSBC). GitHub pull requests may have reviewers assigned to them. It should be possible to synchronize the list of pull request reviewers and the list of a linked Collaborator review's participants.
AWS Code Commit Support
Howdy, Please add Code Collaborator support for AWS Code Commit repository integrations to the web client. Example of this current functionality can be found here: https://support.smartbear.com/collaborator/docs/source-control/git.html https://support.smartbear.com/collaborator/docs/source-control/repo-hosting/index.html In the same way that Github, Bitbucket, and Azure can easily be integrated to the Collaborator, I would like for this process to also function with AWS Code Commit Repos. I may currently use Code Collab and AWS Code Commit via the client gui and local changes, but I would also like to have direct repo integration like the hosted repos do. Thanks.
Version Control Server setup for GIT
When attempting to "Test Connection" after configuring the parameters for a valid cloned repo on the Collab server. I receive the following error: Error: Invalid input: Version control server configuration error: Current directory is not controlled by a Git repository. See attached screenshot of the config and error. This is a valid git repo cloned on the collab server. I can use the same repo from the Collab Client GUI without issue to add to reviews. This collab server has GIT installed which is how I cloned the repo and I am able to git pull and check the git status without issue from the server. The server is a Windows Server 2022 Standard. Any thoughts?
Reviews of a submodule change need to show file change in review
When using a git submodule with a pull request / merge request mechanism enforced (i.e., Bitbucket), when the developer changes the submodule and there is no other change in the parent repository other than pointing to the new merge commit, Collaborator shows no files in the review. Commits are properly listed, but there are no changes to actually review, which is incorrect. Bitbucket, for example, lists the "pointer file" that holds the submodule commit reference. It would be extremely helpful to have Collaborator show this difference as well.
Usage of Collaborator
Is there a way to know how our users are using Collaborator? I want to check if they are using it for document review, or code review? I checked the SCM table in the dB and could only find record of each SCM server. How can I know if the code review was done and when was it done? Thanks in advance.
