You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment there is no check on the existence of the pyproject.toml file in our doc build actions. However, this file is leveraged to decide which backend should be used in our CICD, see
if grep -q 'build-backend = "poetry\.core\.masonry\.api"' "pyproject.toml"; then
.
If this is a requirement then we should put it somewhere in the documentation. If that's not the case then we should fix the current action to add this check. Note that this would help projects which have no pyproject.toml file, e.g. projects mainly composed of examples. Currently, I'm not sure that they are able to use the doc-build action.
Note: speaking of projects without pyproject.toml file, we could use pip as default backend in those cases. What do you think ?
The text was updated successfully, but these errors were encountered:
At the moment there is no check on the existence of the
pyproject.toml
file in our doc build actions. However, this file is leveraged to decide which backend should be used in our CICD, seeactions/_doc-build-linux/action.yml
Line 188 in 8643c5a
actions/_doc-build-linux/action.yml
Line 198 in 8643c5a
If this is a requirement then we should put it somewhere in the documentation. If that's not the case then we should fix the current action to add this check. Note that this would help projects which have no
pyproject.toml
file, e.g. projects mainly composed of examples. Currently, I'm not sure that they are able to use thedoc-build
action.Note: speaking of projects without
pyproject.toml
file, we could usepip
as default backend in those cases. What do you think ?The text was updated successfully, but these errors were encountered: