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

Templates are always taken from main #331

Closed
abizjak opened this issue Aug 19, 2023 · 3 comments
Closed

Templates are always taken from main #331

abizjak opened this issue Aug 19, 2023 · 3 comments
Assignees
Labels
[Type] Task An additional feature or improvement.

Comments

@abizjak
Copy link
Member

abizjak commented Aug 19, 2023

Task description

cargo concordium init

always takes the templates from main. This is a bit problematic since we often have unreleased changes on main and it is awkward to make those without breaking something.

Instead of defaulting to main, we should specify a tag in cargo generate invocation.

We should support a special template/latest tag that we'd update each time we release new concordium-std, and this should be the default tag, and then we should also support normal release tags, e.g., concordium-std/7.1.0.

This would also make it simpler for us to develop.

@abizjak abizjak added the [Type] Task An additional feature or improvement. label Aug 19, 2023
@abizjak
Copy link
Member Author

abizjak commented Aug 19, 2023

@DOBEN @limemloh Any thoughts?

@limemloh
Copy link
Collaborator

Seems like a reasonable approach, maybe even have template releases separate from concordium-std such that we can update these without updating concordium-std.

@rasmus-kirk
Copy link
Contributor

Solved with #419 and this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Task An additional feature or improvement.
Projects
None yet
Development

No branches or pull requests

3 participants