)]}'
{
  "commit": "0c4529747546bf9a6208df8455de6413aa1eee98",
  "tree": "d3dcce2e64ae2ec2da8193515b64890420110008",
  "parents": [
    "8ad0ba0b36762cf4bd6bceaf8dd56a43a9c3d3da"
  ],
  "author": {
    "name": "juj",
    "email": "jujjyl@gmail.com",
    "time": "Wed Aug 27 14:59:01 2025 +0300"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Aug 27 14:59:01 2025 +0300"
  },
  "message": "Allow switching between overrides (#1588)\n\nPreviously, if one used e.g. command\n\n```\nemsdk install --override-repository emscripten-main-64bit@https://github.com/juj/emscripten/tree/my_own_emscripten_branch emscripten-main-64bit\n```\n\nthen the overridden installation would create a git clone from\n`juj/emscripten`, and that clone would be located under the default\nremote name `origin`.\n\nThis would prevent being able to switch between overrides on subsequent\n`emsdk install` commands. I.e. it would then not be possible to later do\na default\n\n```\nemsdk install emscripten-main-64bit\n```\n\ncommand without an override, since the remote name `origin` would point\nto `juj/emscripten` instead of `emscripten-core/emscripten`.\n\nThis PR changes the naming scheme of `git clone`s when\n`--override-repository` is used, to name the clones with remote names\nfrom the override, so in the above case, the clone would appear under\nremote name `juj` and not `origin`.\n\nThis enables flipping between multiple `emsdk install` commands in the\nsame checkout, without needing to nuke the installed directory in\nbetween.\n\nThis enables me to run experiments like\ngithub.com/emscripten-core/emscripten/pull/25025 locally on my CI,\nwithout needing to merge them upstream to become available.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "22c08386d0fefc24369648aba1879f96227b6c85",
      "old_mode": 33188,
      "old_path": "emsdk.py",
      "new_id": "1a553d4b5fd0cc7e4ff75dfa2e9767ab7e980024",
      "new_mode": 33188,
      "new_path": "emsdk.py"
    }
  ]
}