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
AFAIK, rust-ci is looking for my documentation ./doc/. However, cargo now builds the docs inside the target directory (./target/doc). It would be nice if rust-ci automatically looked in the place cargo uses by default :-)
The text was updated successfully, but these errors were encountered:
@tomaka hmm, I haven't looked at the cargo doc command recently. Are there flags that can be passed to it? I feel like the developer should be responsible to build the docs using whatever process seems right to them. For instance, if you didn't want cargo to run the doc tests but rust-ci forced the doc tests to run, that would be really annoying. I think just looking in the default location is sufficient.
AFAIK, rust-ci is looking for my documentation ./doc/. However, cargo now builds the docs inside the target directory (./target/doc). It would be nice if rust-ci automatically looked in the place cargo uses by default :-)
The text was updated successfully, but these errors were encountered: