When this workflow runs, create a report of pull requests that have been merged in the past 24 hours. Post the report to the #engineering-standup Slack channel.
The report will function as a standup update, so it should be detailed and specific because the audience is engineers who work in this codebase. General terms such as "various bug fixes" or "miscellaneous refactors" are not allowed. Instead, be specific about what bug was fixed or what classes/methods were refactored. Write your report in markdown.
The top line should use an emoji to depict how many PR's were merged (see the example below). The line below that should explain the repositories (or "all repositories") that were included and the time period for the report.
To create the report, first identify logical groups of work in the recently merged code. Each logical group of work will get it's own section. The section should be tied to a specific feature, enhancement, refactor, or improvement. Examples of good sections are "API Session Management Enhancements", "Changes to `StripeCheckoutClient`", "Changes to `/user` endpoints", or "Frontend Dashboard". These are good titles for sections because they are specific and descriptive. Examples of bad titles would be "Codebase Refactoring and Cleanup", "Logging and Error Handling", or "Bug Fixes and Stability Improvements". These sections aren't specific enough to warrent a section. Also add a label to the section describing what type of work was done (Feature, Refactor, Bug Fix, etc.).
Then, for each section, list up the 8 bullet points containing the most important changes for that section. The first bullet point should list the pull requests associated with this section (including links to those PRs).
If there are no recently merged pull requests, post a message explaining that.
Here's a markdown example of a report with 2 PR's merged in the past day, and only 1 section:
---
# 2️⃣ PR's merged
in myrepo in the past day
## API Session Management Enhancements (Feature, Refactor)
• 2 pull requests: [#4475](https://github.com/ellipsis-dev/ellipsis/pull/4475), [#4476](https://github.com/ellipsis-dev/ellipsis/pull/4476)
• Renamed the backend module from api_token to api_session, introducing a new public_access_token field for enhanced security and updated model and database row definitions.
• Developed new frontend components such as ApiHomeTab, CreateApiKeyModal, and ApiTokensTable to manage API keys, including creation, listing, and deactivation.
• Introduced API session management models (ApiSessionExternal, ApiSessionInternal, ApiSessionStatus) and a SQLModel representation (ApiSessionsRow) to support session operations.
• Added API endpoints for creating, retrieving, and deleting API sessions, integrated with Slack notifications for better monitoring.
• Extended PostgresClient with new methods to handle API sessions by access token and customer ID, improving database interaction efficiency.
