Remove unused workflows

.github/pull_request_template.md

@@ -14,74 +14,3 @@
 - [ ] Existing unit/integration tests
 - [ ] New unit/integration tests
 - [ ] Manual tests
-
-<!-- Attach code, screenshot, video used for manual testing here. -->
-
-### 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.
-
-<!-- Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change. -->
-
-#### What component(s), interfaces, languages, and integrations does this PR affect?
-
-Components
-
-- [ ] `area/tracking`: Tracking Service, tracking client APIs, autologging
-- [ ] `area/models`: MLmodel format, model serialization/deserialization, flavors
-- [ ] `area/model-registry`: Model Registry service, APIs, and the fluent client calls for Model Registry
-- [ ] `area/scoring`: MLflow Model server, model deployment tools, Spark UDFs
-- [ ] `area/evaluation`: MLflow model evaluation features, evaluation metrics, and evaluation workflows
-- [ ] `area/gateway`: MLflow AI Gateway client APIs, server, and third-party integrations
-- [ ] `area/prompts`: MLflow prompt engineering features, prompt templates, and prompt management
-- [ ] `area/tracing`: MLflow Tracing features, tracing APIs, and LLM tracing functionality
-- [ ] `area/projects`: MLproject format, project running backends
-- [ ] `area/uiux`: Front-end, user experience, plotting, JavaScript, JavaScript dev server
-- [ ] `area/build`: Build and test infrastructure for MLflow
-- [ ] `area/docs`: MLflow documentation pages
-
-<!--
-Insert an empty named anchor here to allow jumping to this section with a fragment URL
-(e.g. https://github.com/mlflow/mlflow/pull/123#user-content-release-note-category).
-Note that GitHub prefixes anchor names in markdown with "user-content-".
--->
-
-<a name="release-note-category"></a>
-
-#### 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.
-
-<details>
-<summary>What is a minor/patch release?</summary>
-
-- Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
-  Bug fixes, doc updates and new features usually go into minor releases.
-- Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
-  Bug fixes and doc updates usually go into patch releases.
-
-</details>
-
-<!-- Do not modify or remove any text inside the parentheses. Keep both checkboxes below. -->
-
-- [ ] 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)

.github/workflows/README.md

@@ -8,14 +8,7 @@
 | `examples.yml`            | Run tests for example scripts & projects                             |
 | `master.yml `             | Run unit and integration tests                                       |
 
-## Automation
-
-| File                        | Role                                                           |
-| :-------------------------- | :------------------------------------------------------------- |
-| `autoformat.yml`            | Apply autoformatting when a PR is commented with `autoformat`  |
-| `autoformat.js`             | Define utility functions used in the `autoformat.yml` workflow |
-| `labeling.yml`              | Automatically apply labels on issues and PRs                   |
-| `notify-dco-failure.yml`    | Notify a DCO check failure                                     |
-| `notify-dco-failure.js`     | The main script of the `notify-dco-failure.yml` workflow       |
-| `release-note-category.yml` | Validate a release-note category label is applied on a PR      |
-| `release-note-category.js`  | The main script of the `release-note-category.yml` workflow    |
+> Note: This fork intentionally omits upstream-only governance workflows
+> (maintainer approval, release-note validation, automatic patch labeling,
+> autoformat, team-review helpers, etc.) because they depend on MLflow's
+> internal GitHub App credentials and Databricks review teams.