-
Notifications
You must be signed in to change notification settings - Fork 178
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
Create manuscript repo without rootstock commit history #398
Comments
Hi Eric! We've played around with a squashing all rootstock commits upon creating a manuscript in #65. The main problem is that it becomes much harder to pull rootstock updates in the future.
I agree it's undesirable to clone the entire rootstock commit history. In the long-term, we hope to switch to using a GitHub template repo that would be located at https://github.com/manubot/template. But for now we don't have a great solution to creating a manuscript without the rootstock commit history.
Yes, In summary, I'd caution against squashing everything to start unless you're willing to do extra maintenance work down the road. But if you'd like to squash, happy to help you debut any further issues.
Any subsequent issues? |
Ok, I'll use as intended then.
Nope! Had to replace master with main everywhere in manubot.yaml (so far only that), but the |
Nice. This issue is in relation to https://github.com/pystatgen/sgkit-publication right? |
Yep. |
Hey @dhimmel, OOC I tried creating a repo fresh instead of from a clone as suggested in https://github.com/manubot/rootstock/blob/master/SETUP.md. I did that to avoid bringing in the commit history from the rootstock repo. Is there a way to make this work? The first problem I ran into is in get_rootstock_commit when running
build.sh
.Are there other ways you would recommend to keep the paper repo up-to-date with the template repo?
The text was updated successfully, but these errors were encountered: