It will simplify the user life, if we have a tag per version like the 17.0.2/17.0.3.
And a version linked to a released and pre-released editor 6000.1.0a6, 6000.0.29f1, 6000.0.0b15, … With a tag guarantee us to have a full green Unit_Tests and Graphics_Tests.
Like that if I take a tagged commit, like that I’ll be sure to have a full green yamato and tests.
Need can be anyone with a custom SRP, or a modifed SRP.
A simple usecase is a local modification of HDRP (the best SRP, thanks for the hardwork against the windmills).
And when I update the editor sometime it not work, and I have to test commits + stash/reapply until it work.
It would simplify our life to have the tag on github.
If it’s too hard to produce a tag per SRP version or/and editor version like it was done before a simple txt file with the SHA of a commit would do the job.
For instance what commit should fit for 6000.1a6, what commit is guaranted to compile with 17.0.3 or 6000.1a6?
Thanks for your help.