[Feature] Allows filtering branch name patterns to which we want to attach a CI job

[daviibf]

Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Context

In our company, we use a mono-repo paradigm where all DBT models are stored alongside other code in the same repository. This results in numerous pull requests (PRs) from various teams, creating the need for more granular control over CI job execution.

Problem

Currently, there is no straightforward way to trigger CI jobs exclusively for PRs or commits related to DBT. Without this capability, unnecessary CI jobs may run for unrelated changes, consuming resources and complicating workflows.

Describe alternatives you've considered

Introduce the ability to trigger CI jobs based on specific branch name patterns or tag names. For example:

• Branches for DBT-related PRs could follow a naming convention like dbt-feat/.
• A CI job could then be configured to trigger only for branches matching this pattern.

Benefits

• Efficiency: Reduces unnecessary CI job executions for unrelated changes.
• Focus: Allows teams to isolate DBT-related CI runs for improved debugging and resource allocation.
• Scalability: Supports the mono-repo setup by enabling teams to define patterns for their own workflows.

Who will this benefit?

• This feature would streamline CI workflows and better support teams working within a mono-repo structure.
• It would also allow writing tests for specific uses cases, using a branch-name convention.

Are you interested in contributing this feature?

No response

Anything else?

No response