Summary
Currently we've started to track dlls published and exported to Unity in git. Every time there's a change to one of the solutions in the src folder we have to publish and export these dlls to Unity, we should automate this process on remote/GitHub using CI.
Suggested features or ways to address the summary
We're already doing this for tests CI in .github\workflows\unity_tests.yml we simply need to persist those changes using an extra commit. We also should change workflow ordering. The two workflows with extra commits should run before we run any other actions, we can even optimize workflow to the point where nothing extra needs to run if previous steps have failed.
Motivation
This will mean remote's main will always have the latest dependencies! And by automating the process we can ignore the Library packages in .gitignore again and Dev doesn't have to worry about pushing the latest dependencies.
Summary
Currently we've started to track dlls published and exported to Unity in git. Every time there's a change to one of the solutions in the
srcfolder we have to publish and export these dlls to Unity, we should automate this process on remote/GitHub using CI.Suggested features or ways to address the summary
We're already doing this for tests CI in
.github\workflows\unity_tests.ymlwe simply need to persist those changes using an extra commit. We also should change workflow ordering. The two workflows with extra commits should run before we run any other actions, we can even optimize workflow to the point where nothing extra needs to run if previous steps have failed.Motivation
This will mean remote's
mainwill always have the latest dependencies! And by automating the process we can ignore the Library packages in.gitignoreagain and Dev doesn't have to worry about pushing the latest dependencies.