Set the `rev` to a version instead of `master`

[soderluk]

"pre-commit assumes that the value of rev is an immutable ref (such as a tag or SHA) and will cache based on that. Using a branch name (or HEAD) for the value of rev is not supported and will only represent the state of that mutable ref at the time of hook installation (and will NOT update automatically)."

https://pre-commit.com/#using-the-latest-version-for-a-repository

Would be beneficial if the yaml also includes the latest version to be used.

[TekWizely]

Hi @soderluk and thanks for taking the time to open an issue!

So, are you suggesting that, in the Installation snippet and in the sample-config.yaml, we update the rev: master to be something immutable?

Honestly, that's a great idea ... I'll add steps to update those as part of preparing versioned releases.

I have one coming up soon and will make sure to update it then, but I might go ahead and set the current release version as the ref in the master branch now ...

In the meantime, I'll keep this open until that next release as reminder.

Thanks again for taking the time and I hope you're otherwise enjoying using the project!

[soderluk]

@TekWizely exactly. It would be great if it would automatically point to the latest release tag. I assume most people will just copy the example and paste it. As did I, and got an error when running it.
Thanks!

[TekWizely]

@soderluk I've updated current master, but I'm going to leave this open until after my next release version, to make sure i start the habit :)

[TekWizely]

@soderluk Now that I've done a release and add a step to update the rev of the sample files, I'm comfortable closing this issue.

Thanks for taking the time and for using my project!

[soderluk]

@TekWizely awesome! Thank you 🙂