pitchfork
semver
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pitchfork
-
Best practice for cpp projects using CMake
Just use cmake-init which sets you up with a variation of the pitchfork layout.
-
Pitchforks: A (de facto) Standard Project Layout for C / C++ projects
Link broken, should be https://github.com/vector-of-bool/pitchfork
-
I'm getting deeper in C++
I use a variation of thispitchfork github layout. I have found it a very useful structure for my projects. As for file names, I always have only one class per file with the file name matching the class name exactly.
-
What's a good resource for learning project architecture ?
Take a look at the pitchfork standard - a lot of projects follow this convention today: https://github.com/vector-of-bool/pitchfork
-
C++ Meson build project template review.
Consider using the pitchfork layout convention
-
Where to put C++ headers and libraries?
This is what I was directed to in regards to this question and what I use to organise structure. I was told it's a good starting point so not sure if there is something better out there. https://github.com/vector-of-bool/pitchfork
- Suggestions for Best Books to Master C++
- c++ terminal program to create projects
-
How would I build a project with cmake?
A while ago I stumbled upon this pitchfork project layout, But for simple projects I have just one CMakefile with the few sources in one project inside. If this grows, I use this and put it in a subfolder of the new project and add_subdirectory it...
semver
-
The right development flow: Better than Agile
We increase the version of our product as specified in SemVer and deploy it to production, preferably following good deployment practices to have no downtime.
-
Git commit helper: add emojis to your commits
Using Conventional Commits β as a standard for your commit messages, makes Semantic Versioning π as easy as can be, with tools like Conventional Changelog π Standard Version π and Semantic Release π¦π
-
Why write a library?
Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.
-
Node package managers (npm, yarn, pnpm) - All you need to know
npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.
-
Snyk CLI: Introducing Semantic Versioning and release channels
We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.
-
Master the Art of Writing and Launching Your Own Modern JavaScript and Typescript Library in 2024
Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.
-
Using semantic-release to automate releases and changelogs
Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH
-
Essential Command Line Tools for Developers
Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-releaseβ¦
-
Testing Our Tasks
The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?
-
What is Semantic Versioning and why you should use it for your software ?
For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org
What are some alternatives?
cmake-init - The missing CMake project initializer
react-native - A framework for building native applications using React
modern-cmake
semantic-release - :package::rocket: Fully automated version management and package publishing
meson_prog_cpp - Trilobite Coder - (Meson build project for C++ application development)
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
pitchforkhttps:
changesets - π¦ A way to manage your versioning and changelogs with a focus on monorepos
cmake_conan_boilerplate_template - Minimized version of cpp_starter_project
helmfile - Deploy Kubernetes Helm Charts
moderncpp-project-template - A Modern C++ cross-platform Project Template with CMake, conan (optional), cppcheck (optional) and clang-format (optional)
Poetry - Python packaging and dependency management made easy