Closed ChaseBENNC9 closed 1 year ago
This is the Build in my fork before the changes and this is the build in my fork after the changes
this is the hash I was talking about earlier. The issue was the long hash key changes every time the project went to build so it couldn't find the one that was already there
One issue that I know of is this that I don't think if it will affect the next build because the cache does not exist yet.
Ready for review. there isn't much to physically look at but you can see the above screenshots to show the improvements and i will also leave link to the actions if you want to look at the process. https://github.com/ChaseBENNC9/Space-Rescue/actions/runs/6103371877 here it is with the updated code https://github.com/ChaseBENNC9/Space-Rescue/actions/runs/5957236603 here it is with the old code I have also created another workflow that will run on wednesdays and should restore the cache when it expires so it should'nt be gone by the time we go to build. i am currently testing it in m fork
This key will be the same every release and significantly reduces the amount of time that the build and release job takes
Describe your changes
This is going to significantly reduce the amount of time the building takes when merging into main. It changes the restore key to a specific name rather than creating a random hash which causes it to be unable to find it.
Issue number and link
188
Checklist before requesting a review