Skip to content

Conversation

@jonas-schievink
Copy link
Contributor

No description provided.

@jonas-schievink jonas-schievink force-pushed the ci branch 5 times, most recently from e845000 to c7d15e4 Compare February 24, 2021 15:11
@jonas-schievink jonas-schievink marked this pull request as draft February 24, 2021 15:31
run: cargo install cargo-generate --debug
- name: Instantiate template
run: |
git config --global init.defaultbranch main
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you also try to git configure:

git config --global user.name "Your Name"
git config --global user.email "[email protected]"

IIRC that causes once for me on a ci run also a problem. See our workflow config

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, that didn't seem to do anything here

override: true
target: ${{ env.TARGET }}
- name: debug
run: cd app-template && git status && ls -la
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here you cd into the app-template, I'm not sure if that would not affect further steps, so that below the cargo generate --git app-template --name out would fail because you are in the folder already?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm, doesn't look like that's the cause either

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

Successfully merging this pull request may close these issues.

3 participants