.conda/benchcab-dev.yaml: remove inclusion of mkdocs-requirements.txt#338
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #338 +/- ##
==========================================
+ Coverage 68.28% 69.60% +1.32%
==========================================
Files 21 21
Lines 1157 1214 +57
==========================================
+ Hits 790 845 +55
- Misses 367 369 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ccarouge
left a comment
There was a problem hiding this comment.
I'm not certain here. That's the quick solution but it's when we work on developments that we need a local install of mkdocs. It's a lot faster to deal with formatting etc. if we build the docs locally than pushing to GitHub to build the preview.
I know that copying the requirements in 2 places (benchcab-dev.yaml and mkdocs-requirements.txt) is not great but removing installing mkdocs in the dev environment is annoying.
|
Just confirmed that copying the contents of mkdocs-requirements.txt into benchcab-dev.yaml (under I will update. |
This is work around for initialising pixi environments from
benchcab-dev.yaml. Pixi has problems handling the -r input when
setting up the environment via pixi init --import:
Error: × Can't parse '-r mkdocs-requirements.txt' as pypi dependency
╰─▶ Expected package name starting with an alphanumeric character, found `-`
-r mkdocs-requirements.txt
^
5fa03c9 to
7415287
Compare
This is work around for initialising pixi environments from benchcab-dev.yaml. Pixi has problems handling the -r input when setting up the environment via
pixi init --import $(realpath $HOME/benchcab)/.conda/benchcab-dev.yaml: