Problem Statement: When connecting Bamboo to a large GitHub Organization (10,000+ repos), the discovery process is synchronous and lacks filtering. This causes the reverse proxy to time out (502 Bad Gateway) because Bamboo attempts to fetch all repository metadata before responding to the UI.

Proposed Feature: Add a "Repository Filter" field in the GitHub Resource configuration screen.

+Filter Type: +*Support for Regular Expressions (Regex) or Wildcards (e.g., proj-alpha-).

Mechanism: Apply the filter as a query parameter during the API call to GitHub or filter the stream before processing the full list into memory.

Benefits for Enterprise:

Reduced Load: Prevents 502 Proxy errors and "zombie" threads that run for 15+ minutes.

Security: Ensures only relevant project repositories are pulled into the Bamboo environment.