{"version":"2.1.223","anchor":"pr-status-cache-can-be-persisted-through-the-storage-backend","canonical_anchor":"pr-status-cache-can-be-persisted-through-the-storage-backend","heading":"PR status cache can be persisted through the storage backend","tier":"soon","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/pr-status-cache-can-be-persisted-through-the-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### PR status cache can be persisted through the storage backend\n\nYour cached pull request statuses could be stored outside a local file, but currently aren't.\n\n**What**\n\nThe cached GitHub PR status map can now be loaded and saved through a storage key rather than only a file on disk.\n\n**Details**\n\n- the separate file-only reader and writer were replaced by a single function taking an optional backend\n- dedicated debug lines are logged when the load or persist step fails\n- with no backend passed, file behaviour is retained\n\n**Evidence**\n\n`persistPrStatusCache: `\n\n- Area: Git Integration\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}