Contributions
Re: Client Maintenance - upgrade to latest version compatible with the server
I would agree that it should be an optional setting as there must be a variety of usage scenarios. We, too, currently have a specific version defined for usage on the shop floor. In our case, it was to ensure a homogeneous environment to simplify our internal support. However, if I assume the client-server relationship is managed safely/correctly and if the updates were appliedconsistently, I should still get a homogeneous environment after a brief period of flux. I am not aware of any specific issues. If I were, I would be advocating for a remedy as being back on an older version potentially forces a client update whena server update is needed. This would create a barrier to upgrade. It is my understanding that theclient-server compatibility is fairly generous/accommodating.8.1KViews0likes0CommentsClient Maintenance - upgrade to latest version compatible with the server
The Code Collaborator client is compatible with a fairly wide range of server versions. The client is aware of the associated server. Ideally, the client tool could auto update when enabled to the current version that is compatible with the associated server version.8.1KViews0likes4CommentsGitLab Support
Code Collaborator has support for GitHub. Ideally, this would also be available and documented for GitLab. There is some overlap between the code review in code collaborator and the pull request process. This causes additional work to use code collaborator. This opens up discussion to moving all code reviews to the code read facilities within the GitLab server to streamline the processes.2.5KViews0likes2CommentsProvide Direct Integration for conducting a review within the IDE
Modern IDEs, such as JetBrain's IntelliJ IDEA, have a rich set of inspections and tools to aid a developer in elevating their code quality. If there was a plugin to allow the code reviewer to view and to annotatea code-based review within their IDE, the reviewerwould have a greater set of tools to aid them in reviewing the code. This would also allow thereviewer to have a greater context of the changes and their impact. I am not asking for a tool to facilitate the creation of a code review. I am asking for a plugin to conduct a code review. specifically, we would benefit from an integration with IntelliJ IDEA.972Views0likes0CommentsIntegration of automated static analysis results as another input provided for a code review
When using static analysis tools, such as SonarQube (http://www.sonarqube.org/), it would be ideal if the changeset was able to be scanned and the results provided as feedback within the code collaborator code review. This would allow the human reviewer to see and to comment on the feedback from the machine-driven results. This also would elevate the machine-driven feedback to something akin to another code reviewer. Admittedly, there are developer-centric feedback channels such as sonarlint but these do not facilitate exposing this information to the code reviewer.1.5KViews1like0Comments