# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19098/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19098/merge#subdirectory=libs/skinny

%sh curl -LsSf https://raw.githubusercontent.com/mlflow/mlflow/HEAD/dev/install-skinny.sh | sh -s pull/19098/merge

What changes are proposed in this pull request?

Update the CONTRIBUTING section to remove incorrect old instructions regarding building the main docs with yarn, as the docs folder is now built with npm. Rather than trying to keep the instructions up to date, simply point people to the docs folder README for up-to-date instructions.

How is this PR tested?

• Existing unit/integration tests
• New unit/integration tests
• Manual tests

Screenshot:

Does this PR require documentation update?

• No. You can skip the rest of this section.
• Yes. I've updated:
  • Examples
  • API references
  • Instructions

Release Notes

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

How should the PR be classified in the release notes? Choose one:

• rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

Yes should be selected for bug fixes, documentation updates, and other small changes. No should be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.

• Yes (this PR will be cherry-picked and included in the next patch release)
• No (this PR will be included in the next minor release)