gitfiti VS semver

Just turn your git history into pixel art

Gitfiti

Git accepts commits in the past. There are tools to make it look however you like -> https://github.com/gelstudios/gitfiti

You can make your past github squares green. This is the reason you can do stuff like this https://github.com/gelstudios/gitfiti

Me: "I needed to make my contribution graph look good"

That's nothing to say about using it though you could really push it over the top by using something like this (or making it yourself for bonus points) to draw images or text on your github activity and drive the point home

There is even a tool[1] to draw images in commit history (so called gitifi).

It is possible because git allows to create and push commit with arbitrary date, using GIT_AUTHOR_DATE env variable or --date flag.

[1]: https://github.com/gelstudios/gitfiti

No one cares about commit history. There are even tools to jokingly spoof commit history. No one takes it seriously anymore. For example https://github.com/gelstudios/gitfiti

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.

Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH

Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…

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?

For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org

I believe neovim follows semantic versioning. https://semver.org/

Semver has been 2.0.0 for 10 years, look at the date of the assets. Multiple releases created today where none existed before. Not sure why someone is creating releases now, perhaps just some housekeeping/cleanup.

https://github.com/semver/semver/releases

All ELRS hardware will talk to all other ELRS hardware, including Radiomaster's ELRS transmitters and receivers. There are one or two exceptions from scummy companies that have been pilloried by the community, and you probably won't find them anymore. So long as the ELRS firmware running on both devices has the same major version number, you're good to go. ie. 3.3.1 will still talk to 3.0.1, but won't talk to 2.0.0. (The "major version" is the 1st number, the "minor version" is the 2nd number, and the "patch version" is the 3rd number. See Semantic Versioning for more info.)

If you're using semver, read the spec it's not overly long or hard to understand.

Semantic versioning actually has a clear rule about this: