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
Should we use version tagging on the main branch, so that big changes to workflows don’t break repo’s that use those workflows.
At the moment, the Readme says use workflow_name@main, which is fine but I could see that breaking if we made a major change to a workflow that was in use. For example, changing a default argument on main might have side effects for consumers that automatically run the latest version.
On the other hand, maintaining versions across consuming workflows would be extra overhead too, so I could see an argument for using main and just fixing workflows when we make breaking changes.
The text was updated successfully, but these errors were encountered:
Versioning might protect us from unexpected changes in the Azure CLI, if we explicitly version it here.
On the other hand, keeping the Azure CLI up-to-date then becomes another small job that might be forgotten. I don’t think there’s a dependabot for Actions (could well be wrong.)
Should we use version tagging on the main branch, so that big changes to workflows don’t break repo’s that use those workflows.
At the moment, the Readme says use
workflow_name@main
, which is fine but I could see that breaking if we made a major change to a workflow that was in use. For example, changing a default argument on main might have side effects for consumers that automatically run the latest version.On the other hand, maintaining versions across consuming workflows would be extra overhead too, so I could see an argument for using
main
and just fixing workflows when we make breaking changes.The text was updated successfully, but these errors were encountered: