[FAKE] GMM IC PR for comment

.binder/runtime.txt

@@ -1 +1 @@
-python-3.9
+python-3.12

.circleci/config.yml

@@ -3,7 +3,7 @@ version: 2.1
 jobs:
   lint:
     docker:
-      - image: cimg/python:3.10.16
+      - image: cimg/python:3.11
     steps:
       - checkout
       - run:
@@ -57,6 +57,7 @@ jobs:
   doc:
     docker:
       - image: cimg/base:current-22.04
+    resource_class: medium+
     environment:
       - MKL_NUM_THREADS: 2
       - OPENBLAS_NUM_THREADS: 2

.codecov.yml

@@ -19,11 +19,9 @@ coverage:
 
 codecov:
   notify:
-    # Prevent coverage status to upload multiple times for parallel and long
-    # running CI pipelines. This configuration is particularly useful on PRs
-    # to avoid confusion. Note that this value is set to the number of Azure
-    # Pipeline jobs uploading coverage reports.
-    after_n_builds: 6
+    # Prevent codecov from calculating the coverage results before all expected uploads
+    # are in. This value is set to the total number of jobs uploading coverage reports.
+    after_n_builds: 7
 
 ignore:
 - "sklearn/externals"

.devcontainer/devcontainer.json

@@ -0,0 +1,18 @@
+{
+  // More info about Features: https://containers.dev/features
+  "image": "mcr.microsoft.com/devcontainers/base:ubuntu-24.04",
+  "features": {},
+
+  "onCreateCommand": ".devcontainer/setup.sh",
+  "postCreateCommand": "",
+
+  "customizations": {
+    "vscode": {
+      "extensions": [
+        "ms-python.python",
+        "ms-toolsai.jupyter"
+      ],
+      "settings": {}
+    }
+  }
+}

.devcontainer/setup.sh

@@ -0,0 +1,20 @@
+#!/bin/bash
+
+set -e
+
+"${SHELL}" <(curl -Ls micro.mamba.pm/install.sh) < /dev/null
+# .bashrc has been updated by the mamba install one-liner above.
+# 'source $HOME/.bashrc' sets up micromamba for later use
+source $HOME/.bashrc
+
+micromamba env create -f build_tools/circle/doc_environment.yml -n sklearn-dev --yes
+# Install additional packages:
+# - ipykernel: to be able to use the VS Code Jupyter integration
+# - pre-commit: avoid linting issues
+micromamba install pre-commit ipykernel -n sklearn-dev --yes
+# install pre-commit hooks
+micromamba activate sklearn-dev
+pre-commit install
+
+# Auto-activate sklearn-dev in terminal
+echo "micromamba activate sklearn-dev" >> $HOME/.bashrc

.git-blame-ignore-revs

@@ -46,3 +46,9 @@ ff78e258ccf11068e2b3a433c51517ae56234f88
 
 # PR 31226: Enforce ruff/pygrep-hooks rules
 b98dc797c480b1b9495f918e201d45ee07f29feb
+
+# PR 31817: Consistently use relative imports
+4abf564cb4ac58d61fbbe83552c28f764284a69d
+
+# PR 31847 Switch to absolute imports enforced by ruff
+1fe659545c70d9f805c1c4097dd2fce9a6285a12

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -10,9 +10,11 @@ body:
       addressed by searching through [the past issues](https://github.com/scikit-learn/scikit-learn/issues).
 - type: textarea
   attributes:
-    label: Describe the bug
+    label: Describe the bug and give evidence about its user-facing impact
     description: >
-      A clear and concise description of what the bug is.
+      A clear and concise description of what the bug is and **how it affects you as a scikit-learn user**. Please give a few details about the context of the discovery, why you care about getting it fixed. Please do not create issues for problems you don't actually care about.
+
+      The scikit-learn issue tracker is swamped by reports and pull-requests. Stating the expected user impact is critical to help maintainers and other contributors focus time and effort to review meaningful contributions.
   validations:
     required: true
 - type: textarea
@@ -36,13 +38,15 @@ body:
       model = lda_model.fit(lda_features)
       ```
 
+      If possible, craft a reproducer that only uses the public scikit-learn API or justify why you had to use some private API to trigger the problem. This helps us assess the user-facing impact of the bug.
+
       If the code is too long, feel free to put it in a public gist and link it in the issue: https://gist.github.com.
 
-      In short, **we are going to copy-paste your code** to run it and we expect to get the same result as you.
+      In short, **we need to be able to quickly copy-paste your code** to run it without modification and we expect to get the same result as you.
 
       We acknowledge that crafting a [minimal reproducible code example](https://scikit-learn.org/dev/developers/minimal_reproducer.html) requires some effort on your side but it really helps the maintainers quickly reproduce the problem and analyze its cause without any ambiguity. Ambiguous bug reports tend to be slower to fix because they will require more effort and back and forth discussion between the maintainers and the reporter to pin-point the precise conditions necessary to reproduce the problem.
     placeholder: |
-      ```
+      ```python
       Sample code to reproduce the problem
       ```
   validations:
@@ -89,6 +93,14 @@ body:
       ```
   validations:
     required: true
+- type: textarea
+  attributes:
+    label: Interest in fixing the bug
+    description: >
+      If your issue is triaged by project maintainers as a bug that can be reproduced, would you be interested in working on a PR to resolve it? 
+      And if you already have an idea, please explain your analysis of the root cause of the bug and a strategy for a possible fix, but please do not open a PR as long as the issue has not been triaged.
+  validations:
+    required: true
 - type: markdown
   attributes:
     value: >

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -6,7 +6,7 @@ body:
 - type: markdown
   attributes:
     value: >
-      #### If you want to propose a new algorithm, please refer first to the [scikit-learn inclusion criterion](https://scikit-learn.org/stable/faq.html#what-are-the-inclusion-criteria-for-new-algorithms).
+      #### If you want to propose a new algorithm, please refer first to the [scikit-learn inclusion criterion](https://scikit-learn.org/dev/faq.html#what-are-the-inclusion-criteria-for-new-algorithms).
 - type: textarea
   attributes:
     label: Describe the workflow you want to enable

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,16 @@
 <!--
-Thanks for contributing a pull request! Please ensure you have taken a look at
-the contribution guidelines: https://github.com/scikit-learn/scikit-learn/blob/main/CONTRIBUTING.md
+🙌 Thanks for contributing a pull request!
+
+👀 Please ensure you have taken a look at the contribution guidelines:
+https://github.com/scikit-learn/scikit-learn/blob/main/CONTRIBUTING.md
+
+✅ In particular following the pull request checklist will increase the likelihood
+of having maintainers review your PR:
+https://scikit-learn.org/dev/developers/contributing.html#pull-request-checklist
+
+📋 If your PR is likely to affect users, you will need to add a changelog entry
+describing your PR changes, see:
+https://github.com/scikit-learn/scikit-learn/blob/main/doc/whats_new/upcoming_changes/README.md
 -->
 
 #### Reference Issues/PRs
@@ -15,17 +25,27 @@ is merged. See https://github.com/blog/1506-closing-issues-via-pull-requests
 #### What does this implement/fix? Explain your changes.
 
 
+#### AI usage disclosure
+<!--
+If AI tools were involved in creating this PR, please check all boxes that apply
+below and make sure that you adhere to our Automated Contributions Policy:
+https://scikit-learn.org/dev/developers/contributing.html#automated-contributions-policy
+-->
+I used AI assistance for:
+- [ ] Code generation (e.g., when writing an implementation or fixing a bug)
+- [ ] Test/benchmark generation
+- [ ] Documentation (including examples)
+- [ ] Research and understanding
+
+
 #### Any other comments?
 
 
 <!--
-Please be aware that we are a loose team of volunteers so patience is
-necessary; assistance handling other issues is very welcome. We value
-all user contributions, no matter how minor they are. If we are slow to
-review, either the pull request needs some benchmarking, tinkering,
-convincing, etc. or more likely the reviewers are simply busy. In either
-case, we ask for your understanding during the review process.
-For more information, see our FAQ on this topic:
+Thank you for your patience. Changes to scikit-learn require careful
+attention, but with limited maintainer time, not every contribution can be reviewed
+quickly.
+For more information and tips on improving your pull request, see:
 https://scikit-learn.org/dev/faq.html#why-is-my-pull-request-not-getting-any-attention.
 
 Thanks for contributing!

.github/workflows/autoclose-comment.yml

@@ -0,0 +1,67 @@
+name: autoclose comment
+# Post comment on PRs when labeled with "autoclose".
+
+permissions:
+  contents: read
+  pull-requests: write
+
+on:
+  pull_request_target:
+    types:
+      - labeled
+
+env:
+  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+  GH_REPO: ${{ github.repository }}
+  PULL_REQUEST_NUMBER: ${{ github.event.pull_request.number }}
+
+jobs:
+
+  post_comment:
+    name: post_comment
+    if: github.event.label.name == 'autoclose'
+    runs-on: ubuntu-latest
+
+    steps:
+
+      - name: comment on potential autoclose
+        run: |
+          gh api \
+          --method POST \
+          -H "Accept: application/vnd.github+json" \
+          -H "X-GitHub-Api-Version: 2022-11-28" \
+          /repos/$GH_REPO/issues/$PULL_REQUEST_NUMBER/comments \
+          -f "body=$BODY"
+        env:
+          BODY: >
+            ⏰ This pull request might be automatically closed in two weeks from now.
+
+
+            Thank you for your contribution to scikit-learn and for the effort you have
+            put into this PR. This pull request does not yet meet the quality and
+            clarity needed for an effective review. Project maintainers have limited
+            time for code reviews, and our goal is to prioritize well-prepared
+            contributions to keep scikit-learn maintainable.
+
+
+            To increase the chance of a productive review, please refer to: [How do I
+            improve my issue or pull
+            request?](https://scikit-learn.org/dev/faq.html#how-do-i-improve-my-issue-or-pull-request)
+            As the author, you are responsible for driving this PR, which entails doing
+            necessary background research as well as presenting its context and your
+            thought process. If you are a [new
+            contributor](https://scikit-learn.org/dev/developers/contributing.html#new-contributors),
+            or do not know how to fulfill these requirements, we recommend that you
+            familiarise yourself with scikit-learn's development conventions via other
+            contribution types (e.g., reviewing PRs) before submitting code.
+
+
+            Scikit-learn maintainers cannot provide one-to-one guidance on this PR.
+            However, if you ask focused, well-researched questions, a community
+            member may be willing to help. 💬
+
+
+            If you substantially improve this PR within two weeks, a team member may
+            remove the `autoclose` label and the PR stays open. Cosmetic changes or
+            incomplete fixes will not be sufficient. Maintainers will assess
+            improvements on their own schedule. Please do not ping (`@`) maintainers.

.github/workflows/autoclose-schedule.yml

@@ -0,0 +1,35 @@
+name: autoclose schedule
+# Autoclose labeled PR after 2 weeks.
+
+permissions:
+  contents: read
+  pull-requests: write
+
+on:
+  schedule:
+    - cron: '0 2 * * *' # runs daily at 02:00 UTC
+  workflow_dispatch:
+
+env:
+  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+jobs:
+
+  autoclose:
+    name: autoclose labeled PRs
+    runs-on: ubuntu-latest
+    if: github.repository == 'scikit-learn/scikit-learn'
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-python@v6
+        with:
+          python-version: '3.13'
+      - name: Install PyGithub
+        run: pip install -Uq PyGithub
+
+      - name: Checkout repository
+        uses: actions/checkout@v6
+
+      - name: Close PRs labeled more than 14 days ago
+        run: |
+          python build_tools/github/autoclose_prs.py