Add bot_author checks to skip ETR automation for bot PRs

[vim-zz]

✨ PR Description

Purpose: Add bot author checks to skip Estimated Time to Review (ETR) automation for bot-created pull requests.
Main changes:

• Added bot_author detection rule for identifying automated PR authors using pattern matching
• Updated ETR automation condition to skip processing when PR author is a bot
• Applied consistent bot detection across multiple automation rules for better maintainability

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using. We'd love your feedback! 🚀}

[orca-security-us]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Infrastructure as Code	0   0   0   0	View in Orca
Passed	SAST	0   0   0   0	View in Orca
Passed	Secrets	0   0   0   0	View in Orca
Passed	Vulnerabilities	0   0   0   0	View in Orca

[gitstream-cm]

✨ PR Review

The PR adds bot author detection to skip ETR automation for bot-generated PRs, which is a good improvement. However, the implementation has significant code duplication and structural inconsistencies.

2 issues detected:

🧹 Maintainability - Identical logic repeated multiple times increases maintenance burden and risk of inconsistent updates.

Details: The bot_author detection logic is duplicated 4 times throughout the file with identical template expressions. This violates the DRY principle and creates maintenance overhead when the bot detection criteria need to be updated.
File: docs/managed-mode.md

🧾 Readability - Inconsistent structural organization makes the configuration harder to understand and follow.

Details: The is: sections are placed inconsistently - some immediately follow automation blocks, others appear at section boundaries. This creates confusion about proper scope and organization.
File: docs/managed-mode.md

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using. We'd love your feedback! 🚀}

[gitstream-cm]

A screenshot of the relevant part of docs after the changes is a life saver 🛟

[MishaKav]

can you remove the escaping in all exmaples please (they come becase i took it from logs)

Suggested change

	is:
	bot_author: {{ pr.author | match(list=[\"github-actions\", \"_bot_\", \"[bot]\", \"dependabot\"]) | some }}
	is:
	bot_author: {{ pr.author | match(list=["github-actions", "_bot_", "[bot]", "dependabot"]) | some }}

[claude]

PR Review: Add bot_author checks to skip ETR automation for bot PRs

Code Quality Assessment: ✅ APPROVE

Positive aspects:

• Consistent implementation of bot_author condition across all relevant automations
• Good reuse of the is.bot_author expression following DRY principles
• Clear intent - effectively excludes bot PRs from ETR automation
• Uses appropriate regex patterns for common bot naming conventions

Potential improvements:

• Consider expanding bot detection patterns to include renovate, greenkeeper, etc.
• The is.bot_author definition is repeated 4 times - could add documentation note about shared conditions

Assessment summary:

• No security risks - only affects automation triggers
• Efficient implementation using short-circuiting some filter
• No performance concerns
• Documentation-only change, no unit tests required
• Low risk, high value improvement

This change effectively prevents ETR automation from running on bot PRs, improving both resource utilization and workflow clarity.

Rating: ✅ APPROVED - Clean implementation following gitStream best practices.