We analyze changes2 and, if there are no errors, we accept the merge request, otherwise reject it.īy the way, if you are interested in analyzing commits and pull requests for C/C++, you are welcome to read about it here. This is how a merge request looks like before introducing a static analyzer: Therefore, I suggest adding a merge request check. Moreover, when merging branches, we have a list of changed files. We also don't want to analyze the entire project every time. The main point of checking is to make sure that problems detected by the analyzer do not make it into the master branch when merging. The difference will be in getting a list of files for analysis and will depend on which systems you are using. If you are interested in configuring checks of commits or pull requests, you can also do this using this mode. To check certain files, specify the -sourceFiles ( -f) flag and pass. But since this is not very convenient, we have added the ability to pass. xml to the analyzer with a list of files. Previously, in order to check certain files, one had to pass. 检查文件列表的方式 (Mode of checking a list of files ) Can analyze the code meant for 32-bit, 64-bit and embedded ARM platforms. Works in 64-bit systems on Windows, Linux and macOS. Enjoy the reading and have a nice unicorn mood. Today we will tell you how to configure the PVS-Studio C# analyzer for checking merge requests. Do you like GitLab and don't like bugs? Do you want to improve the quality of your source code? Then you've come to the right place.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |