Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: Version tagging #10

Open
eatyourgreens opened this issue Feb 11, 2022 · 1 comment
Open

RFC: Version tagging #10

eatyourgreens opened this issue Feb 11, 2022 · 1 comment

Comments

@eatyourgreens
Copy link
Contributor

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.

@eatyourgreens
Copy link
Contributor Author

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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant