Welcome to the ZDoom Forums!

[quote="Rachael"]Yes. If you are compiling without Git and using the zip files instead, use the hash code for that zip - it can be found on the last commit message next to the zip download.[/quote]
Ye, that's my preferred way of compiling at the moment, just downloading the master as a .zip then taking care of it. I'll provide it in my future bug reports :3: .

Yes. If you are compiling without Git and using the zip files instead, use the hash code for that zip - it can be found on the last commit message next to the zip download.

I've noticed long ago that the master .zip files also contain a hash/code, would that be useful too?

The same applies to "latest", "current", "March 13th", and so on. A commit time has nothing to do with a push time, they are unrelated.
Commit hashes exist for this reason, to uniquely identify the state of source code.
You want to point to a particular commit, post a hash, or better insert a GitHub link to it.

If you are self-compiling and reporting bugs, please post the commit hash.

If you are unsure, simply type "git describe --tags" in your source tree. Or type "git rev-parse HEAD". If using a devbuild, simply open your INI and copy the first line.

Use whichever format you like best. Either way though, don't use "HEAD".