{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":617547449,"defaultBranch":"main","name":"mrsk","ownerLogin":"djmb","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2023-03-22T16:02:54.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/1734607?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1679501128.0","currentOid":""},"activityList":{"items":[{"before":"65b90dd5c8d362468286ca5bf67762bcb8784897","after":"1ed4a37da2b73125c37044d04e5a9a5ba0efd62a","ref":"refs/heads/default-to-deploying-config-version","pushedAt":"2023-03-23T14:39:44.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"djmb","name":"Donal McBreen","path":"/djmb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1734607?s=80&v=4"},"commit":{"message":"Pull latest image tag, so we can identity it\n\n`docker image ls` doesn't tell us what the latest deployed image is (e.g\nif we've rolled back). Pull the latest image tag through to the server\nso we can use it instead.","shortMessageHtmlLink":"Pull latest image tag, so we can identity it"}},{"before":"83dc82661b8a02dd1fbb0ee91261104cee127862","after":"f73c526890430f1653e79a973119789bcb2f94d7","ref":"refs/heads/main","pushedAt":"2023-03-23T14:37:54.874Z","pushType":"push","commitsCount":23,"pusher":{"login":"djmb","name":"Donal McBreen","path":"/djmb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1734607?s=80&v=4"},"commit":{"message":"Ask for access token","shortMessageHtmlLink":"Ask for access token"}},{"before":"fb3353084f903c16d9b367d55d12adbd4f917a2d","after":"65b90dd5c8d362468286ca5bf67762bcb8784897","ref":"refs/heads/default-to-deploying-config-version","pushedAt":"2023-03-23T13:42:32.000Z","pushType":"push","commitsCount":27,"pusher":{"login":"dhh","name":"David Heinemeier Hansson","path":"/dhh","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2741?s=80&v=4"},"commit":{"message":"Merge branch 'main' into default-to-deploying-config-version","shortMessageHtmlLink":"Merge branch 'main' into default-to-deploying-config-version"}},{"before":"45a0d6752470cf95c7a6709bf04f8e67fa168122","after":"fb3353084f903c16d9b367d55d12adbd4f917a2d","ref":"refs/heads/default-to-deploying-config-version","pushedAt":"2023-03-22T16:15:00.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"djmb","name":"Donal McBreen","path":"/djmb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1734607?s=80&v=4"},"commit":{"message":"Default to deploying the config version\n\nIf we don't supply a version when deploying we'll use the result of\ndocker image ls to decide which image to boot. But that doesn't\nnecessarily correspond to the one we have just built.\n\nE.g. if you do something like:\n\n```\nmrsk deploy        # deploys git sha AAAAAAAAAAAAAA\ngit commit --amend # update the commit message\nmrsk deploy        # deploys git sha BBBBBBBBBBBBBB\n```\n\nIn this case running `docker image ls` will give you the same image\ntwice (because the contents are identical) with tags for both SHAs but\nthe image we have just built will not be returned first. Maybe the order\nis random, but it always seems to come second as far as I have seen.\n\ni.e you'll get something like:\n\n```\nREPOSITORY    TAG              IMAGE ID       CREATED          SIZE\nfoo/bar       AAAAAAAAAAAAAA   6272349a9619   31 minutes ago   791MB\nfoo/bar       BBBBBBBBBBBBBB   6272349a9619   31 minutes ago   791MB\n```\n\nSince we already know what version we want to deploy from the config,\nlet's just pass that through.","shortMessageHtmlLink":"Default to deploying the config version"}},{"before":"a15f3f289f4fa0854861855c8f300c55c604ccea","after":"45a0d6752470cf95c7a6709bf04f8e67fa168122","ref":"refs/heads/default-to-deploying-config-version","pushedAt":"2023-03-22T16:07:45.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"djmb","name":"Donal McBreen","path":"/djmb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1734607?s=80&v=4"},"commit":{"message":"Default to deploying the config version\n\nIf we don't supply a version when deploying we'll use the result of\ndocker image ls to decide which image to boot. But that doesn't\nnecessarily correspond to the one we have just built.\n\nE.g. if you do something like:\n\n```\nmrsk deploy        # deploys git sha AAAAAAAAAAAAAA\ngit commit --amend # update the commit message\nmrsk deploy        # deploys git sha BBBBBBBBBBBBBB\n```\n\nIn this case running `docker image ls` will give you the same image\ntwice (because the contents are identical) with tags for both SHAs but\nthe image we have just built will not be returned first. Maybe the order\nis random, but it always seems to come second as far as I have seen.\n\ni.e you'll get something like:\n\n```\nREPOSITORY    TAG              IMAGE ID       CREATED          SIZE\nfoo/bar       AAAAAAAAAAAAAA   6272349a9619   31 minutes ago   791MB\nfoo/bar       BBBBBBBBBBBBBB   6272349a9619   31 minutes ago   791MB\n```\n\nSince we already know what version we want to deploy from the config,\nlet's just pass that through.","shortMessageHtmlLink":"Default to deploying the config version"}},{"before":null,"after":"a15f3f289f4fa0854861855c8f300c55c604ccea","ref":"refs/heads/default-to-deploying-config-version","pushedAt":"2023-03-22T16:05:28.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"djmb","name":"Donal McBreen","path":"/djmb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1734607?s=80&v=4"},"commit":{"message":"Default to deploying the config version\n\nIf we don't supply a version when deploying we'll use the result of\ndocker image ls to decide which image to boot. But that doesn't\nnecessarily correspond to the one we have just built.\n\nE.g. if you do something like:\n\n```\nmrsk deploy        # deploys git sha AAAAAAAAAAAAAA\ngit commit --amend # update the commit message\nmrsk deploy        # deploys git sha BBBBBBBBBBBBBB\n```\n\nIn this case running `docker image ls` will give you the same image\ntwice (because the contents are identical) with tags for both SHAs but\nthe image we have just built will not be returned first. Maybe the order\nis random, but it always seems to come second as far as I have seen.\n\ni.e you'll get something like:\n\n```\nREPOSITORY    TAG              IMAGE ID       CREATED          SIZE\nfoo/bar       AAAAAAAAAAAAAA   6272349a9619   31 minutes ago   791MB\nfoo/bar       BBBBBBBBBBBBBB   6272349a9619   31 minutes ago   791MB\n```\n\nSince we already know what version we want to deploy from the config,\nlet's just pass that through.","shortMessageHtmlLink":"Default to deploying the config version"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyMy0wMy0yM1QxNDozOTo0NC4wMDAwMDBazwAAAAMJx2z9","startCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wMy0yM1QxNDozOTo0NC4wMDAwMDBazwAAAAMJx2z9","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wMy0yMlQxNjowNToyOC4wMDAwMDBazwAAAAMJAeKZ"}},"title":"Activity · djmb/mrsk"}