)]}'
{
  "commit": "200fdfbdce72acfff65d38b692cede474ff505e1",
  "tree": "08f19e69d2a625020f97078b53d480db40814a65",
  "parents": [
    "930175323f94100e95203edb9efe9359c52cd69b"
  ],
  "author": {
    "name": "Tong Mu",
    "email": "dkwingsmt@users.noreply.github.com",
    "time": "Wed Oct 14 22:30:30 2026 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Oct 14 22:30:30 2026 +0000"
  },
  "message": "Move Material/Cupertino PRs from design triage to framework triage (#194244)\n\nRemoves the \"Legacy Design Languages PRs\" link from the design team\nsection of `docs/triage/README.md`. The Framework PR list query no\nlonger excludes the `f: material design`, `f: cupertino`, `p:\nmaterial_ui`, and `p: cupertino_ui` labels, so those PRs now show up in\nframework triage.\n\nThe design triage meeting discussed this, and both the ecosystem and\nframework teams agreed:\n\n- Legacy design PRs opened during the decoupling effort have had enough\ntime to migrate to flutter/packages. Inactive ones are being closed.\n- New PRs that touch the frozen Material and Cupertino libraries in\nflutter/flutter should not make semantic changes. They should mostly be\nminor maintenance, like lint fixes or repo-wide refactors. Whether to\naccept them into the frozen libraries is typically a call for framework\nteam, not for the design triage.\n\nDesign language PRs in flutter/packages are still tracked by the\nexisting \"Design Language PRs\" link.\n\n\n## Pre-launch Checklist\n\n- [ ] I read the [Contributor Guide] and followed the process outlined\nthere for submitting PRs.\n- [ ] I read the [AI contribution guidelines] and understand my\nresponsibilities, or I am not using AI tools.\n- [ ] I read the [Tree Hygiene] wiki page, which explains my\nresponsibilities.\n- [ ] I read and followed the [Flutter Style Guide], including [Features\nwe expect every widget to implement].\n- [ ] I signed the [CLA].\n- [ ] I listed at least one issue that this PR fixes in the description\nabove.\n- [ ] I updated/added relevant in-code documentation (doc comments with\n`///`).\n- [ ] If this PR introduces a new feature or capability, I created and\nlinked a website documentation issue or PR in [flutter/website] (or\nverified none is needed).\n- [ ] I added new tests to check the change I am making, or this PR is\n[test-exempt].\n- [ ] I followed the [breaking change policy] and added [Data Driven\nFixes] where supported.\n- [ ] All existing and new tests are passing.\n\nIf you need help, consider asking for advice on the #hackers-new channel\non [Discord].\n\nIf this change needs to override an active code freeze, provide a\ncomment explaining why. The code freeze workflow can be overridden by\ncode reviewers. See pinned issues for any active code freezes with\nguidance.\n\n**Note**: The Flutter team is currently trialing the use of [Gemini Code\nAssist for\nGitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code).\nComments from the `gemini-code-assist` bot should not be taken as\nauthoritative feedback from the Flutter team. If you find its comments\nuseful you can update your code accordingly, but if you are unsure or\ndisagree with the feedback, please feel free to wait for a Flutter team\nmember\u0027s review for guidance on which automated comments should be\naddressed.\n\n\u003c!-- Links --\u003e\n[Contributor Guide]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview\n[AI contribution guidelines]:\nhttps://github.com/flutter/flutter/blob/main/CONTRIBUTING.ai.md\n[Tree Hygiene]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md\n[test-exempt]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests\n[Flutter Style Guide]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md\n[Features we expect every widget to implement]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement\n[CLA]: https://cla.developers.google.com/\n[flutter/tests]: https://github.com/flutter/tests\n[flutter/website]: https://github.com/flutter/website\n[breaking change policy]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes\n[Discord]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md\n[Data Driven Fixes]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0336a1407716ffa84cd0cbc04a4fc6c9f91b5056",
      "old_mode": 33188,
      "old_path": "docs/triage/README.md",
      "new_id": "6647a69608cca35645661de0107fef8952915fae",
      "new_mode": 33188,
      "new_path": "docs/triage/README.md"
    }
  ]
}