Better Handling When the Repo in A User's Cookiecutter Cache Uses a origin
Remote Other than Expected
#1158
Labels
bug
A crash or error in behavior.
Describe the bug
The current usage and handling of the cookiecutter cache operates irrespective of where the
origin
remote actually lives. This can create situations where the cache exists for the repo but theorigin
remote is not what's expected or even explicitly requested.Steps to reproduce
briefcase-android-gradle-template
:rm -rf ~/.cookiecutters/briefcase-android-gradle-template
pyproject.toml
of a forked repo, e.g.:template = "https://github.com/rmartin16/briefcase-android-gradle-template"
briefcase create android
pyproject.toml
briefcase create android
againrmartin16
repo instead of thebeeware
repoExpected behavior
In the least, Briefcase should warn the user the cache is using an
origin
remote that doesn't match what's being requested.The more complete change would probably update the
origin
remote, fetch, and then checkout the head for the specified template ref.Screenshots
No response
Environment
0.3.14.dev75+g9bb5444c.d20230331
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: