{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":255617816,"defaultBranch":"release","name":"hackage-search","ownerLogin":"serokell","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2020-04-14T13:32:52.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/13840520?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1709640003.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"0f261ff388db4046ea321aae33d69db1ab337386","ref":"refs/heads/sereja/OPS-1161-harden-services","pushedAt":"2024-03-05T12:00:03.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Sereja313","name":null,"path":"/Sereja313","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/112060595?s=80&v=4"},"commit":{"message":"[OPS-1161] Harden systemd service\n\nProblem: We want to harden the security of our systemd services.\n\nSolution: Use the hardening profile defined in serokell.nix.","shortMessageHtmlLink":"[OPS-1161] Harden systemd service"}},{"before":"5e419b781cfa8db2d02baf6f4e5734c40b3f4cf3","after":null,"ref":"refs/heads/sereja/OPS-1402-add-restart-policy","pushedAt":"2024-01-17T06:12:05.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"delete-merged-branch[bot]","name":null,"path":"/apps/delete-merged-branch","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/14757?s=80&v=4"}},{"before":"c7eeea63d22e0d9e4405a0e5125296ad4af87643","after":"0e63784207fc866b6f8b656a27dd9173715fcddf","ref":"refs/heads/release","pushedAt":"2024-01-17T06:12:02.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"Sereja313","name":null,"path":"/Sereja313","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/112060595?s=80&v=4"},"commit":{"message":"Merge pull request #31 from serokell/sereja/OPS-1402-add-restart-policy\n\n[Chore] Add systemd unit restart policy","shortMessageHtmlLink":"Merge pull request <a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2053775966\" data-permission-text=\"Title is private\" data-url=\"https://github.com/serokell/hackage-search/issues/31\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/serokell/hackage-search/pull/31/hovercard\" href=\"https://github.com/serokell/hackage-search/pull/31\">#31</a> from serokell/sereja/OPS-1402-add-restart-policy"}},{"before":null,"after":"5e419b781cfa8db2d02baf6f4e5734c40b3f4cf3","ref":"refs/heads/sereja/OPS-1402-add-restart-policy","pushedAt":"2023-12-22T11:16:33.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Sereja313","name":null,"path":"/Sereja313","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/112060595?s=80&v=4"},"commit":{"message":"[Chore] Add systemd unit restart policy\n\nProblem: By default, systemd services generated from the NixOS system configuration don't attempt to restart on failure since Restart=no. However, in some cases, running processes can fail for unclear reasons, and the simplest way to bring the failed service back to life is to restart it. Instead, currently, the service will fail and trigger an alert without attempting to restart.\n\nSolution: Add default values for startLimitBurst, startLimitIntervalSec, Restart, and RestartSec.","shortMessageHtmlLink":"[Chore] Add systemd unit restart policy"}},{"before":"fa52281a8f25e8efaf692e192892b834e206ac88","after":null,"ref":"refs/heads/rvem/update-nix-usage-in-ci","pushedAt":"2023-03-20T03:49:33.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"delete-merged-branch[bot]","name":null,"path":"/apps/delete-merged-branch","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/14757?s=80&v=4"}},{"before":"29011cfd8e87949569e56e264967120ba65ce237","after":"c7eeea63d22e0d9e4405a0e5125296ad4af87643","ref":"refs/heads/release","pushedAt":"2023-03-20T03:49:30.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"rvem","name":"Roman Melnikov","path":"/rvem","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14182218?s=80&v=4"},"commit":{"message":"Merge pull request #30 from serokell/rvem/update-nix-usage-in-ci\n\n[Chore] Don't use old 'nix run' command","shortMessageHtmlLink":"Merge pull request <a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"1628693427\" data-permission-text=\"Title is private\" data-url=\"https://github.com/serokell/hackage-search/issues/30\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/serokell/hackage-search/pull/30/hovercard\" href=\"https://github.com/serokell/hackage-search/pull/30\">#30</a> from serokell/rvem/update-nix-usage-in-ci"}},{"before":null,"after":"fa52281a8f25e8efaf692e192892b834e206ac88","ref":"refs/heads/rvem/update-nix-usage-in-ci","pushedAt":"2023-03-17T05:00:17.044Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"rvem","name":"Roman Melnikov","path":"/rvem","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14182218?s=80&v=4"},"commit":{"message":"[Chore] Don't use old 'nix run' command\n\nProblem: 'nix run' interface has changed with flake addition.\nHowever, CI pipeline in this repo still uses the old 'nix run'\nfor which we keep a workaround on our build servers.\n\nSolution: Use 'nix shell' instead.","shortMessageHtmlLink":"[Chore] Don't use old 'nix run' command"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEDMi-VQA","startCursor":null,"endCursor":null}},"title":"Activity · serokell/hackage-search"}