Add size trends report step to CI workflow #133
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On every push to the master branch, size data will be written to a Google Sheets spreadsheet. This information will allow tracking the trends in memory usage over time.
|
Memory usage change @d38082cc4f401465f04b4f43e290014f08d6fa3e
|
aentinger
approved these changes
Jun 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On every push to the master branch, size data will be written to a Google Sheets spreadsheet.
This information will allow tracking the trends in memory usage over time.
The first row of data (in addition to the column headings row) should written to the spreadsheet when this PR is merged.
Question: do you think it's best to have a single spreadsheet for the size trends reports for all repositories (one sheet in the spreadsheet per repository), or a separate spreadsheet for each repository. The former seems more convenient, but my concern is that we could hit some limit at a distant date in the future when there are lots of repositories with trends reports. The latter results in more clutter by having multiple spreadsheets.
If we are planning to go with the single spreadsheet approach, I'd add the
sheet-name: ArduinoIoTCloudinput to the workflow in this PR.