Improve commit messages to deadlock-data repo

[hassayag]

Current commit messages are just a generic "reparsed data". For PRs this is fine, but the commit history needs something for each case:

push - MERGE [v0.2.1-5555] - deadlock-wiki/deadbot@1234567 , where we have the version, build num, and commit hash referencing the one on deadbot
workflow-dispatch - DISPATCH [v0.2.0rev5-5555] - deadbot
pull-request - PR - deadlock-wiki/deadbot#88

To support this, we would also need some logic to increment the version

[B13rg]

For the increment version logic, is it the version of the gamefiles or the version of deadbot?

If it's the deadbot tagged version, parse it out from the pyproject.toml file?

Separate from this, it might be nice to have some deadbot release automation, unless we want to just have a "rolling release" and just run whatever's in the master branch

[hassayag]

For the increment version logic, is it the version of the gamefiles or the version of deadbot?

Both, in the example v0.2.1 is the deadbot version, and 5555 is the build number you find inside steam.inf

If it's the deadbot tagged version, parse it out from the pyproject.toml file?

Yep! Would need some auto increment system. Eg. merge into develop increments the revision ("rev"), and merge into master will be a manual increment depending on whether its a match, major, or breaking change. Could try semantic commit messaging to handle that though

Separate from this, it might be nice to have some deadbot release automation, unless we want to just have a "rolling release" and just run whatever's in the master branch

I'd love more detail on this. At the moment there is no release system, but in my head it will be a case of saying every few weeks "oh develop looks good and stable, lets merge it into master". But I'm willing to explore other things, since the wiki moves very fast at this current stage