CircleCI Ideas logo
CircleCI Ideas
Create
Home
Feedback
Feature Requests
1247

    Boards

  • Feature Requests

  • Server

  • Orbs

  • Images

  • Insights & Reporting

  • Documentation

  • API

  • Runner

  • Webhooks & Notifications

  • VS Code Extension

  • CLI

  • Config

  • CD & Release Orchestration

  • Identities & Permissions

Powered by Canny

Feature Requests

Tell us what you'd like to see added to CircleCI.

Category

      • Config
      • Monorepo
      • Workflow Mgmt
      • Build & Deploy
      • Contexts
      • VCS-Specific Asks
      • Security
      • UI & UX
      • Plans & Pricing
      • Legacy Functionality
      • Other
      • Dynamic Config (Set-up jobs)
      • IP Ranges (open preview)
      • Testing
      • Roles & Permissions
      • Caching
      • Uncategorized
Monorepo Support and/or filtering based on VCS changes in a specific directory
Currently, any merges to master trigger all steps of all workflows. In an monorepo that houses multiple projects, this results in multiple redundant steps as, for example, the backend is re-tested and re-deployed even if only frontend changes have been made. It is currently possible to do: workflows: flow: jobs: - deploy: filters: branches: only: - master It would be useful for all teams that run a monorepo to also be able to specify, say: workflows: flow: jobs: - terraform: filters: modified_paths: only: - /^infrastructure/ - deploy: requires: terraform filters: modified_paths: only: - /^app/ CCI-I-208
58
·

complete

Powered by Canny