-
Notifications
You must be signed in to change notification settings - Fork 1
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
Documenter and refactor #40
Conversation
Merge main into src_refactor_and_docs
I guess if you add the Manifest that would pin them, but I would say we don't really want to do that for a release... We should just create a new release of the packages, and then we don't have to pin them. If the whole issue is that we need those branches for documentation, we can pin the branches in the CI job that deploys it. I can probably have a look at the CI stuff once this is merged on master. |
Sure we can create a release. Completely understand the point on GridapSolvers, let me know what you both decide.
Sounds good! 👍 |
…STO_Distributed into src_refactor_and_docs
…lows propagation of parameter changes
Enhancing RepeatedAffineFEStateMaps
Automated CI
I'm going to merge this PR. Note that docs and script formatting is still in progress but this branch is massive. |
Changes
src
as discussed in Enhancement for paper: Refactor src, Write docs, Refactor package IO #34src
scripts
andsrc
@JordiManyer, this PR is still on-going work. If you have some time, feel free to have a look at the documentation and see what you think. Feel free to contribute (again if you have some time!).
FYI to call the package we need to add the required branches to the
Project.toml
indocs
(e.g.,Gridap#master
etc.). Does pinning the packages sort this problem out?