NokiMo
Megan Fox
Megan Fox

patreon


Neato changelog tool for Perforce (simplified)

Hola, backers!

(this is a chopped-down version of the code-tier post that ended up pretty big and complicated, just in case the $1+ folks also use Perforce)

So, I'm gonna assume you're all somewhat techy types that might use Perforce or like to as their version control. Which I highly recommend btw, it's a lot more stable than git is with big files, and like... big binary files are most of gamedev. If you're not techy btw, I'd still recommend against git, and instead suggest you maybe just try Unity Collaborate? It doesn't have branching, which is death to coders, but for artist/designer types, especially tiny teams? It's honestly not bad.

Anyways! Let's move on assuming you're using Perforce. Here, a quick present:

Put that in a .bat file, and run it in your Perforce directory, and you'll get a changelog generated instantly! Change the default date if you just want to run it from Windows and have the file dumped, or, run it from command line with an argument like so:

make_changelog 2019/01/08

to get a changelog sweeping in all changes from that date to current date.

Handy, right? No big thing, just, handy! I don't know why that isn't something you can access in p4v's UI, but whatever, now you can just make a .bat file that double clicks and bam. Your testers will thank you.

Now $3+ tier folks can go over here and see how to turn this into simple a button in Perforce, with popup argument entry!

EDIT: (and read the comments, where Ryan suggested a modification you might want to do - thanks Ryan!)

Comments

FYI: If your workflow involves creating numbered but pending-submission CL using p4 change (for code review or other purposes), you'll want to add "-s submitted" to the command line so it only includes submitted CLs in your changelog. :)

UllerRM


Related Creators