Our build automation does not update the submodule, (possibly) unless changes are made to the submodule within this repository, which wed rather avoid.
Currently that means that even when code builds and works, this automation doesn't show it building because its on an outdated submodule version.
Expected Behavior
Ideally, this build automation will constantly pull the submodule to the latest version. This way, when something builds locally when developing (because user has updated their submodule) the automation will show it building too.
Steps to Reproduce
Literally write code that relies on newer embedded-base code and push it, or look at exisitn commits/PRs dealing with this issue
Observed Behavior
Our build automation does not update the submodule, (possibly) unless changes are made to the submodule within this repository, which wed rather avoid.
Currently that means that even when code builds and works, this automation doesn't show it building because its on an outdated submodule version.
Expected Behavior
Ideally, this build automation will constantly pull the submodule to the latest version. This way, when something builds locally when developing (because user has updated their submodule) the automation will show it building too.
Steps to Reproduce
Screenshots (as needed)
No response