Git Reviews

Cppcheck Reviews

Git mentions (229)

• Mastering Version Control with Git: Beyond the Basics

  Official Git Documentation: https://git-scm.com/ - The definitive source for all things Git, with in-depth explanations, commands, and tutorials. Interactive Git Training: https://learngitbranching.js.org/ - A hands-on platform to learn Git fundamentals and experiment with branching and merging in a simulated environment. Git SCM Blog: https://git-scm.com/ - Stay updated on the latest Git developments, news, and... - Source: dev.to / 4 days ago

• Steps to Initialize a Shopify Web App Locally: A Comprehensive Guide

  Git: Version 2.28.0 or higher. Download from git-scm.com. - Source: dev.to / 6 days ago

• Introduction to Git

  To learn more about git and official documentation. - Source: dev.to / 7 days ago

• Why Docs-as-Code is the Key to Better Software Documentation

  Git for version control and GitHub for storing remote versions of the repository. - Source: dev.to / 7 days ago

• pyaction 4.31.0 Released

  This Docker image is designed to support implementing Github Actions With Python. As of version 4.0.0., it starts with The official python docker image as the base Which is a Debian OS. It specifically uses python:3-slim to keep the image size Down for faster loading of Github Actions that use pyaction. On top of the Base, we've installed curl, Gpg, git, and the GitHub CLI. We added curl and gpg because they Are... - Source: dev.to / 9 days ago

Cppcheck mentions (10)

• Configuring Cppcheck, Cpplint, and JSON Lint

  I dedicated Sunday morning to going over the documentation of the linters we use in the project. The goal was to understand all options and use them in the best way for our project. Seeing their manuals side by side was nice because even very similar things are solved differently. Cppcheck is the most configurable and best documented; JSON Lint lies at the other end. - Source: dev.to / 4 months ago

• Enforcing Memory Safety?

  Using infer, someone else exploited null-dereference checks to introduce simple affine types in C++. Cppcheck also checks for null-dereferences. Unfortunately, that approach means that borrow-counting references have a larger sizeof than non-borrow counting references, so optimizing the count away potentially changes the semantics of a program which introduces a whole new way of writing subtly wrong code. Source: about 1 year ago

• Static Code analysis

  For my own projects, I used cppcheck. You can check out that tool to get a feel. Depending on what industry your in, you might need to follow a standard like Misra. Source: about 1 year ago

• How do you not shoot yourself in the foot ?

  Https://cppcheck.sourceforge.io/ (there are many other static analysis tools, I just haven't used them or didn't care for them). Source: about 1 year ago

• Linting tool for prohibiting the use of specific std types

  Sounds like something that could simply be communicated with the team that writes the tests. Unless you have dozens of such classes. In that case, you could just use e.g. Cppcheck and add a rule (regular expression) that searches for usages of the forbidden classes. Source: over 1 year ago