You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would avoid needing to manually re-run the generation script every time there's a change we want reflected.
To avoid redundant execution, ideally each version folder would include a commit hash that can be compared against as part of the action, so re-generation of a given version would only need to occur if and when that branch/tag has actually changed since the previous generation.
An alternative would be doing things via submodules and using an approach like the sync submodules action from the ArduSub docs, but that seems messy given the parameters here aren't already generated and stored in individual branches.
The text was updated successfully, but these errors were encountered:
This would avoid needing to manually re-run the generation script every time there's a change we want reflected.
To avoid redundant execution, ideally each version folder would include a commit hash that can be compared against as part of the action, so re-generation of a given version would only need to occur if and when that branch/tag has actually changed since the previous generation.
An alternative would be doing things via submodules and using an approach like the sync submodules action from the ArduSub docs, but that seems messy given the parameters here aren't already generated and stored in individual branches.
The text was updated successfully, but these errors were encountered: