Send a weekly environment report to Slack
Connect and test the Slack delivery channel before enabling the environment’s weekly report. Each environment has its own schedule setting.
Turn on the weekly report and check delivery#
An organization administrator can turn on one report per environment each week, with a note in the connected channel.
- Open Environments and select the environment.
- Open Setup → Weekly report in the sidebar.
- Select Send a weekly report.
After each week ends (Monday to Sunday, UTC), Proofline keeps the week's report and posts a short note with its link. The note names the environment and the week. It then gives the counts the week recorded:
- deploys verified at landing, 20 minutes, 1 hour and 1 day, out of every deploy recorded from 25 hours before the week began until 25 hours before it ended and after the repository was linked to the environment. A GitHub deploy that never succeeded counts in the window containing its first recorded status. When those deploys went to more than one GitHub Environment, or came from AWS CodePipeline or AWS Amplify, the note first gives each group's count, largest first, named by its GitHub Environment or AWS service, and then the count over every deploy recorded. It names five groups and gives the rest one shared line. The report shows each group's count above Verified at all four checks, which shows the count over every deploy. A GitHub Environment whose deploys change no runtime Proofline reads, such as a package publication, still counts in the total and has its own line;
- those deploys with a recorded regression;
- latent-risk scans started or, when some did not complete, the completed scans out of those started;
- scheduled scans that did not start, with the cause: the organization lacked credits, or the previous scan was still running. When credits were the cause, the line links to organization billing;
- existing problems reported with how many were new, and those fixed through a merged Proofline pull request;
- the fix pull requests opened, their states when Proofline made the report and those merged before the week ended. When a fix rule opened any of them, the note also gives the fix rule's pull requests merged after a Kian re-check of the merged commit found no counterexample, out of all the fix rule's pull requests opened that week.