)]}'
{
  "log": [
    {
      "commit": "7fe19f7b49f4366fcba12b8f3cbef40913370ba9",
      "tree": "b79aff206c2c12a8338d53a79d9071cdb09f91fa",
      "parents": [
        "acae1ef4088e0e9579d7c35b2f7ce1de21c5ac22"
      ],
      "author": {
        "name": "Serge Bazanski",
        "email": "serge@nexantic.com",
        "time": "Wed May 19 12:24:54 2021 +0200"
      },
      "committer": {
        "name": "Sergiusz Bazanski",
        "email": "serge@nexantic.com",
        "time": "Wed May 19 11:28:38 2021 +0000"
      },
      "message": "intellij: fix e2e configurations, remove watcherTasks\n\nEnd-to-end test configurations within IntelliJ were not updated since\nthe metropolis package rename from //core into //metropolis.\n\nAdditionally, the watcherTasks seem to also have been broken forever, as\nthey attempted to build proto paths that didn\u0027t exist, and trigger\ngoimports which we haven\u0027t used for ages. This just removes them, as\nI\u0027m not exactly sure what their intended use was.\n\nChange-Id: I277b642a2b4a6c897150652106eac17cbc8c9732\nReviewed-on: https://review.monogon.dev/c/monogon/+/62\nReviewed-by: Leopold Schabel \u003cleo@nexantic.com\u003e\n"
    },
    {
      "commit": "023093c104fbddc568e624949ec68a5722dcd180",
      "tree": "497fe0f51477767642ad885d089daf9e5659d639",
      "parents": [
        "18b4d653647c23e3a4cd10832d5d6dbd56a4e37e"
      ],
      "author": {
        "name": "Leopold Schabel",
        "email": "leo@nexantic.com",
        "time": "Tue Dec 15 18:48:19 2020 +0100"
      },
      "committer": {
        "name": "Leopold Schabel",
        "email": "leo@nexantic.com",
        "time": "Tue Dec 15 18:48:19 2020 +0100"
      },
      "message": "intellij: add run configurations for fietsje and gazelle\n\nTest Plan: Did the thing\n\nX-Origin-Diff: phab/D662\nGitOrigin-RevId: a2b6da33c09256e78774e83e84972034131fcb77\n"
    },
    {
      "commit": "ede8a80d816f8c102ed4de13ba25512024582a75",
      "tree": "6ac77e0709b7a1422e240323b43d78b838c93bca",
      "parents": [
        "56a7ae643059875a074ab6e3ca92754520483edd"
      ],
      "author": {
        "name": "Leopold Schabel",
        "email": "leo@nexantic.com",
        "time": "Fri Dec 11 14:53:50 2020 +0100"
      },
      "committer": {
        "name": "Leopold Schabel",
        "email": "leo@nexantic.com",
        "time": "Fri Dec 11 14:53:50 2020 +0100"
      },
      "message": "Remove .ijwb and .idea, migrate to import_run_configurations\n\nThe Bazel IntelliJ team has stated that while checking in the .ijwb folder\ntechnically sorta-kinda works, they recommend against it since they cannot\nguarantee any kind of backwards compatibility. Indeed, bootstrapping a\nworking IDE project from a clean checkout with .ijwb has been a\ndelicate matter in the past and is currently broken again.\n\nDo the supported thing instead and nuke .ijwb and .idea and ignore them.\nThe .bazelproject file can then be used to create a new project using\nFile → Import Bazel project, creating the workspace from scratch.\n\nRun configurations are now created by the Bazel plugin, and those XML\nfiles come with a backwards compatibility promise.\n\nThis means that we lose all other shared settings except run\nconfigurations. If there\u0027s particular configs that we want to keep, we\nneed to write custom tooling which mangles the XML configs, which will\nallows us to deal with backwards compatibility and differences in\ndeveloper setups (i.e. outside contributors).\n\nTest Plan:\nCloned the project from scratch, imported the Bazel\nproject, everything worked on the first try :O\n\nX-Origin-Diff: phab/D658\nGitOrigin-RevId: 979ac5345fd8a5f26a5f8ec3d5882ea477b48a69\n"
    }
  ]
}