Open yasu-sh opened 1 year ago
@yuanzhou could you tell me current status on this repository? I am prepared to push with following your readme.md instruction. I made it up to 7th step. just before pull request on 8th step.
Sorry, I will catch up with things--give me a few weeks. I just got overwhelmed with projects.
@jdramsey @yasu-sh Are you trying to update the documentation to this repo? I don't see any pull request.
@jdramsey @kvb2univpitt Are you trying to update the documentation to this repo? I don't see any pull request.
Yesterday I just closed it. Then I re-opened today.
Sorry, I will catch up with things--give me a few weeks. I just got overwhelmed with projects.
No problems. I just thought the my pull-request itself become old. Already mkdocs version became PR's 1.4.3 to 1.5.3 already.
Let me know if this issue should be closed without actions? If so, I will understand my actions was not be efficient, good way.
Let me try to contact Kevin.
I just merged your pull request. Sorry for the delay.
@kvb2univpitt Thanks for your merging! As README says, we need to have review before final pushing to production site. https://bd2kccd.github.io/stage/
Who is appropriate persion for this review..? You , @jdramsey, or some colleagues. If I can move on to the production, let me know. I think 2-3 days will be appropriate.
@yasu-sh I am not sure. I can get back to you on that.
@kvb2univpitt @jdramsey , Can I update the docs? Already 3 months passed, but It must be still good for users. To be checked by developers: https://bd2kccd.github.io/stage/ Outdated docs: https://bd2kccd.github.io/docs/
Can you assign me as a reviewer? I'm not sure...
@jdramsey I tried. Unfortunately I have no permission to assign any reviewers...
Let me try asking a different person for help.
I hope to update some descriptions since I sometimes confused on using causal-cmd. I am ready to fork and update some links including mkdocs updates from mkdocs 1.0.4 to 1.4.2(latest).