Keep track of bundle size for extensions via a non-blocking check about amp-github-apps HOT 3 CLOSED

@danielrozenberg could you move the work plan to a separate comment authored by you? Right now, I'm getting notified each time the comment is edited.

from amp-github-apps.

lol sure, I'll remove it from the description and add it here:

Workplan:

• submit and deploy #428
• after #428 is deployed, create a PR that migrates all .br files to .json (with the proper format of course) → done at ampproject/amphtml-build-artifacts#18
• unrollback #412
• create a new PR that reads bundle-sizes from the .json file instead of the .br file, submit and deploy it → done at #514
• create a PR to receive a JSON payload with multiple bundle sizes when storing → done at #515
• once #514 and #515 are deployed, update the amphtml repo to send to the JSON payload on master builds → done at ampproject/amphtml#24955
• do a switcharoo from /store.json to /store (both on bundle-size bot and in amphtml, make sure to keep in sync) → done at #519 and ampproject/amphtml#24958 and #523
• start storing extensions and other runtime files for master push builds → done at ampproject/amphtml#25042
• create a PR to receive a JSON payload with multiple bundle sizes when reporting → done at #527
• once deployed, update the amphtml repo to report the JSON payload on pull requests → done at ampproject/amphtml#25042
• do a switcharoo from /report.json to /report (wait at least 2 weeks before doing this, to reduce changes of errors in straggling PRs) → done at #577 and ampproject/amphtml#25276 and #584
• delete all .br and extensionless files from https://github.com/ampproject/amphtml-build-artifacts/tree/master/bundle-size
• decide how to report and block PRs that increase bundle size of any files other than dist/v0.js

from amp-github-apps.

Closing since the "keep track" part is done. Work continues in #617

from amp-github-apps.