Best way to test with uncommitted changes?

[macintacos]

I'm working on developing a template, and want to be able to test the template without necessarily needing to commit my changes (since they'll be changing pretty frequently as I prototype). What's the best way to go about doing that?

[mshafer-NI]

What I and my team-mates have done is:

• Make a dev branch
• Go ahead and commit as we work to have copier use the latest committed
• When we think the template is ready - use Git to merge the dev commits (I tend to use rebase -i main) OR, go ahead and post a PR and have it merge with a squash commit.

[yajo]

Just use copier to copy the local template. Since #520, dirty changes should be included. El jue, 18 ago 2022 15:50, Julian Torres ***@***.***> escribió:

…

I'm working on developing a template, and want to be able to test the template without necessarily needing to commit my changes (since they'll be changing pretty frequently as I prototype). What's the best way to go about doing that? — Reply to this email directly, view it on GitHub <#743>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHNXDK4FHPJKQ6RZOOUC53VZY5QRANCNFSM565JETQQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mshafer-NI]

Is this in 6.1.0?

[macintacos]

I'm on 6.1.0, but I've been running with --vcs-ref=HEAD after doing a WIP commit, which seems to be what this PR introduced. Should I not be including that flag anymore?

[macintacos]

When I remove the --vcs-ref=HEAD flag and run it manually after making some minor change (like changing a "help" prompt), I do see the message that says the following, which makes me think that it should be working:

/Users/macinburrito/Library/Caches/pypoetry/virtualenvs/ops-template-t_ulhZ_c-py3.10/lib/python3.10/site-packages/copier/vcs.py:151: DirtyLocalWarning: Dirty template changes included automatically.
  warn(

However, when it shows the prompt that I changed in the copier.yml file I don't see that changes reflected. The only way I can get it to work is if I commit the WIP change manually and add --vcs-ref=HEAD, which seems to be what should already be handled by that PR. Any insight into what I'm doing wrong?

[yajo]

You shouldn't need to commit. Copier should do the commit in another temporary worktree for you.

If you've spotted a bug in that feature, then you will have to provide valid steps to reproduce it. Otherwise I can't fix it 😕

[FlorianLudwig]

I have created a ticket for this bug with a description on how to reproduce it here: #879