\r\n\u003Cimg width=\"857\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e103dc3a-e5c8-4f76-82c9-180a483a3628\" />\r\n\r\nIt looks like every PR has these double deployment. We should only keep one netlify deployment env.\r\n\r\n@vikiival Do you have access to the netlify dashboard?\r\n",[2020],{"name":2021,"color":2022},"A-maintenance","FBCA04",11326,"Double deploy on netlify for all the branchs","2025-02-13T16:33:26Z","https://github.com/kodadot/nft-gallery/issues/11326",0.77146995,{"description":2029,"labels":2030,"number":2041,"owner":1994,"repository":1995,"state":2012,"title":2042,"updated_at":2043,"url":2044,"score":2045},"Time has come and I need to work on other stuff so we've decided to step up automatization\r\n\r\n- [x] check on GitHub workflow and write one in JS/Rust as GH workflow\r\n- [x] generate a new address (and setup identity for the new address)\r\n- [x] parse from pull request, if there is a KSM address of the original author, prefer payout format or we should invent our own URI for this?\r\n- [ ] publish on GitHub marketplace\r\n- [ ] ???\r\n- [ ] PROFIT\r\n- [ ] make the private key as gh secret for now? later as env at netlify?\r\n\r\nCandidates we've found we're in Rust or we can use for now [Probot](https://github.com/probot/probot) as it's few Polkadotjs calls, like sign stuff etc\r\n\r\n### Ref\r\n- [Secrets are not passed to workflows that are triggered by a pull request from a fork. Learn more.](https://docs.github.com/en/actions/security-guides/encrypted-secrets)\r\n- [PolkadotJS](https://polkadot.js.org/docs/api/examples/promise/simple-connect) -- [SimpleConnect](https://polkadot.js.org/docs/api/examples/promise/simple-connect)\r\n- [Make Simple Transfer](https://polkadot.js.org/docs/api/examples/promise/make-transfer)\r\n\r\n\r\n\r\n",[2031,2033,2035,2038],{"name":2032,"color":1989},"$$$",{"name":2034,"color":1992},"p5",{"name":2036,"color":2037},"hackathon","91962A",{"name":2039,"color":2040},"experimental","B09211",1565,"Payout LGTM bot v0","2023-04-25T10:53:32Z","https://github.com/kodadot/nft-gallery/issues/1565",0.7882129,{"description":2047,"labels":2048,"number":2052,"owner":1994,"repository":1995,"state":2012,"title":2053,"updated_at":2054,"url":2055,"score":2056},"idk what has happend but I recall it wasn't happening with first integration so need review tho",[2049],{"name":2050,"color":2051},"p1","D93F0B",2168,"Remove netlify extra comment on pull requests","2022-02-03T11:49:36Z","https://github.com/kodadot/nft-gallery/issues/2168",0.7954978,{"description":2058,"labels":2059,"number":2065,"owner":1994,"repository":1995,"state":2012,"title":2066,"updated_at":2067,"url":2068,"score":2069},"> We recommend you [update your SDK from sentry.javascript.browser@v6.19.7 to sentry.javascript.browser@v7.29.0](https://docs.sentry.io/platforms/javascript) (All sentry packages should be updated and their versions should match)\r\n\r\nSeems we are using not so latest sentry version.\r\n\r\nRecent is 7.0.2 - https://www.npmjs.com/package/@nuxtjs/sentry\r\n\r\nhttps://github.com/kodadot/nft-gallery/blob/main/package.json#L75\r\n\r\nhttps://sentry.nuxtjs.org/guide/migration\r\n\r\n\r\n\r\nMaybe enable lazy-loading? \r\n- https://sentry.nuxtjs.org/sentry/lazy-loading",[2060,2061,2062],{"name":1988,"color":1989},{"name":2007,"color":1992},{"name":2063,"color":2064},"error-tracking","DA1128",4661,"Bump Sentry to recent version, enrich reported events","2023-01-11T15:42:22Z","https://github.com/kodadot/nft-gallery/issues/4661",0.7984005,{"description":2071,"labels":2072,"number":2074,"owner":1994,"repository":1995,"state":2012,"title":2075,"updated_at":2076,"url":2077,"score":2078},"Check netlify for webhooks",[2073],{"name":2007,"color":1992},2044,"Add to Deploys channel only alarm when build is not successfull","2022-04-08T09:57:29Z","https://github.com/kodadot/nft-gallery/issues/2044",0.8007225,{"description":2080,"labels":2081,"number":2087,"owner":1994,"repository":1995,"state":2012,"title":2088,"updated_at":2089,"url":2090,"score":2091},"Hey, it seems Sentry caught every day like over 100 errors (spike is when Pinata did upgrade) and I guess it would be nice to take a peak together on new errors. \r\nThe best what would be if Sentry could automatically log errors to our issues would be my ideal desired scenario, so we don't have many manual work to do and trust machines which actually offload some cognitive load. \r\n\r\n\r\n\r\n\r\n\r\n\r\nA lot of errors are still happening, even with a recent drop.\r\n\r\nSo I've taken a team plan, which has unlimited team members. \r\n\r\nI made @preschian @vikiival admin so they can invite you (@roiLeo) to mitigate some errors people haven't reported here \r\nI'll play with integrations to be more seamless.\r\n\r\nHappy to peak and mitigate many errors and improve the user experience! \r\n\r\n## Replays\r\nI was thinking of using this \r\n- https://docs.sentry.io/platforms/javascript/session-replay/\r\n- https://github.com/kodadot/nft-gallery/issues/4663\r\n\r\n## Profiling\r\nPlus we can resolve some issues taking a while for a good experience\r\n\r\n- https://docs.sentry.io/product/profiling/\r\n\r\n## Others\r\n- https://geekflare.com/frontend-web-monitoring/\r\nI'm not proficient in which error tracking is best, yet happy to adjust, for now going with team plan and mitigating most of errors would be good to go I guess:)\r\n\r\n## Alternatives\r\n- https://www.appsignal.com/\r\n- https://www.airbrake.io/pricing",[2082,2083,2084],{"name":1991,"color":1992},{"name":2063,"color":2064},{"name":2085,"color":2086},"profiling","B1783D",4659,"Sentry team plan ","2023-01-16T09:20:03Z","https://github.com/kodadot/nft-gallery/issues/4659",0.8062399,{"description":2093,"labels":2094,"number":2099,"owner":1994,"repository":1995,"state":2012,"title":2100,"updated_at":2101,"url":2102,"score":2103},"To me looks like a Netlify outage?\r\n\r\n`Deploy did not succeed: Deploy directory 'dist' does not exist`\r\n\r\nFirst failed build seems on `main` at 11:44am\r\n\r\nMy bet is at \r\n\r\nhttps://github.com/kodadot/nft-gallery/pull/2815/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R27\r\n\r\n### Ref\r\n- https://github.com/kodadot/nft-gallery/pull/2812\r\n- https://github.com/kodadot/nft-gallery/pull/2825\r\n- #2718 \r\n\r\nhttps://app.netlify.com/teams/yangwao/builds/625549e849e59900089b0d26\r\n\r\n\r\n\r\nhttps://app.netlify.com/sites/koda-nuxt/deploys/62554a7806c0270008e7f412\r\n\r\n\r\n\r\n",[2095,2096],{"name":2050,"color":2051},{"name":2097,"color":2098},"🧙♀️ - bug-hunt","DC2653",2826,"Builds are broken ","2022-04-12T11:39:00Z","https://github.com/kodadot/nft-gallery/issues/2826",0.80671346,{"description":2105,"labels":2106,"number":2112,"owner":1994,"repository":1995,"state":2012,"title":2113,"updated_at":2114,"url":2115,"score":2116},"We would need to migrate our Pinata implementation right away to join it with implementing Estuary and (wranglers) kv workers from Cloudflare\r\n\r\nIt was mitigate here once we made deploy https://github.com/kodadot/nft-gallery/pull/1853/files#diff-0545e2a376463878833d723ae342d6ce923a4fdc919623bf3cb001e7cb1dec06R6\r\n\r\nbut that's a temporary hotfix. \r\n\r\n### Ref\r\n- #963 \r\n- https://developers.cloudflare.com/pages/platform/functions",[2107,2108,2109],{"name":2050,"color":2051},{"name":2009,"color":2010},{"name":2110,"color":2111},"cloudflare","f6821e",1889,"Rewrite deployment of functions from Netlify to Cloudflare KV workers","2022-01-19T10:50:42Z","https://github.com/kodadot/nft-gallery/issues/1889",0.8097329,["Reactive",2118],{},["Set"],["ShallowReactive",2121],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"ud1bmZ-u_vBM9e3k9gRZeucKtU_yBuBcE936BenWt5M":-1},"/kodadot/nft-gallery/4679"]