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

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

Related Issues/PRs

None.

What changes are proposed in this pull request?

This PR improves the documentation for the prompt_template parameter in
LOG_MODEL_PARAM_DOCS (mlflow/mlflow/utils/docstring_utils.py).

The original description already explained the {prompt} placeholder and listed
the supported pipeline types. This update keeps the existing content intact and
adds a concise Python example demonstrating:

• how to define a prompt template,
• how to log a text-generation pipeline using mlflow.transformers.log_model,
• how the pyfunc flavor applies the template automatically at inference time.

This example makes the intended usage clearer and improves the usability of the
prompt_template feature without changing any behavior.

How is this PR tested?

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

This is a documentation-only change.
Manual verification was performed to ensure that the added example integrates
correctly into the shared docstring, and CI will validate that the documentation
builds without issues.

Does this PR require documentation update?

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

This update enhances the API reference documentation for the prompt_template
parameter by adding a practical example.

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.

Improved documentation for the prompt_template parameter in the transformers
flavor, including a short usage example.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/tracking
• area/models
• area/model-registry
• area/scoring
• area/evaluation
• area/gateway
• area/prompts
• area/tracing
• area/projects
• area/uiux
• area/build
• area/docs

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

• rn/none
• rn/breaking-change
• rn/feature
• rn/bug-fix
• rn/documentation

Should this PR be included in the next patch release?

• 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)