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

Keep track of parent repo #11

Open
thatch opened this issue Oct 20, 2020 · 0 comments
Open

Keep track of parent repo #11

thatch opened this issue Oct 20, 2020 · 0 comments

Comments

@thatch
Copy link
Member

thatch commented Oct 20, 2020

For illustration, my projects look like this

https://github.com/python-packaging/skel

https://github.com/thatch/imperfect (branches main, skel)
local clone (main, skel) referring to (origin/main, origin/skel)

Those two github urls do not share any common ancestors; the repo skel has the code and templates to generate the branch skel. If someone wants a different default license, or changes to defaults (like whether to use codecov.io), they fork that repo.

Towards and eventual goal of e.g. a skelup command/service that runs regen-git for you against a checkout of the appropriate repo skel somewhere, we need to know what the appropriate one is. When running regen-git for the first time (after this change), we can look at that repo skel checkout's origin and record that as the default parent.

Storing this in .vars.ini in a new section seems reasonable.

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

No branches or pull requests

1 participant