-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
Provide a way to opt out of #166 #848
Comments
If I understand you correct:
is this correct? And you are suggesting a configuration like so:
in the template repo to configure the users "active" branch after they have used your template repo? Right? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since #166, the generated template now has the same default branch name as the generated template.
This sometimes can create some issues for templates stored in main branch that matches the code in main branch.
What I want to achieve:
So GitHub Actions can be run to validate the templates on pull requests.
templates
branch by GitHub Actions upon a release.Version numbers inside templates are modified by GitHub Actions automatically by appending to a Rhai script.
(I want to leverage the create release page from GitHub to create a release.
At that time GitHub already tags the release so templates cannot be modified anymore.
It's also a burden for the user to know the latest tag in order to generate from a template.)
However, repositories generated from the
templates
branch will have their default branch set totemplates
.Is it possible to provide a way to specify the default branch name?
e.g.:
So doing
cargo generate user/project --branch templates
will still result in a template with the main branch being created.The text was updated successfully, but these errors were encountered: