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

separate docs subdirectory #125

Closed
ibaned opened this issue Nov 5, 2018 · 4 comments
Closed

separate docs subdirectory #125

ibaned opened this issue Nov 5, 2018 · 4 comments

Comments

@ibaned
Copy link
Contributor

ibaned commented Nov 5, 2018

It would greatly speed up clone times of this repository if the docs subdirectory were moved into a separate Git repository, and its history removed from this one.

@gsjaardema
Copy link
Member

I will do this, but need to figure out which git method to use for the subpackage... SEACAS is used in a few other places and they each use a different subpackage method, so I need to see how best to do this and not break their uses...

@ibaned
Copy link
Contributor Author

ibaned commented Dec 14, 2018

Good to hear! Yes, this can be a tricky decision. I've seen several drawbacks to using git submodules (one of the possible methods). In my opinion the lowest risk is to not associate them at all using git, simply have sufficient advertisement (README, etc) that users know where to find the docs repository without git's help.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 6, 2020

Stale issue message

@gsjaardema
Copy link
Member

This has been done. Docs are now in seacas-docs repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants