Loops for Development & IT, page 4 88 Loops
Code, tests, docs and operations. Narrow down by sub-area, job, tool and level.
Results
Filters
Filters
Check deserialization before merge
Checks every merge request with new or changed input paths for load code that builds objects from untrusted data.
Review package names weekly
Checks new dependencies and internal package names every week for confusion risks and unexpected sources.
Check tenant filters before merge
Checks every merge request that changes data access for queries or cache keys that omit the current tenant.
Review long-running transactions weekly
Checks traces and slow-query logs every week for transactions that stay open too long or wait outside the database.
Check clean shutdown before merge
Checks every merge request that changes stop handlers, workers or deploy settings for work that could be lost when an instance stops.
Review snapshot tests weekly
Looks every week at snapshot tests that grew or were updated often, and proposes targeted assertions for the weakest ones.
Check retries before merge
Checks every merge request that adds or changes retries for error choice, wait time, limits and stacked layers.
Check money handling before merge
Checks every merge request that touches amounts for types, rounding rules and currency handling.
Check time-dependent tests before merge
Checks every merge request with new deadline or time logic for whether tests use a controllable clock and cover the edge cases.
Check shell scripts before merge
Checks every merge request that adds or changes shell scripts for swallowed errors, empty variables and wrong exit codes.
Check for swallowed errors before merge
Checks every merge request that adds or changes error handling for empty handlers, catch-all blocks and silent default values.
Check event ordering before merge
Checks every merge request that changes an event or webhook handler for versions, duplicate detection and safe handling of late events.
Check model routing weekly
Checks once a week whether task types still follow the cost-and-quality routing rules and whether a sample should be re-run.
Check acceptance checks before merge
Checks every merge request started by a coding agent for acceptance checks written before the code change.
Check tool results before merge
Checks every merge request that adds or changes a tool whose text returns into an agent for injection guards.
Check certificates and domains monthly
Checks SSL certificate and domain expiry dates every month and reports anything expiring within 45 days.
No matches. Remove a filter or try another word.