Hi, @cockroach. The “pages changed” count is the number of files ending in
.htm where the checksum of the file has changed since the last published deploy in the same deploy context. The “files changed” count is the same but without the filter for the file extension (it is all files change not just HTML files changed).
The list is calculated on the fly during the deploy and it is not saved anywhere that can be queried via our API. However, you can programmatically use the API to regenerate the list.
You can find the changed file information by querying the API and comparing the SHA checksums for all files in both deploys. There is more information about this API call here:
The files with identical with identical paths and new checksums are “changed”. The files which have no corresponding path in the previous deploy are considered new files (even if it is just the same file checksum just renamed to a new name).
About the number of files changing between deploys, this is typically not directly related to the number of files change in the commit. For example, if you edit a single file which is included as a header in all other files, you can update only a single file in the repo and cause all files in that deploy to change during the site build.
If there are other questions about this, please let us know.