CircleCI "Your config has been disabled" - Uncommitted Config

By Daniel Zoghalchali·Latchkey

CircleCI runs pipelines from the committed .circleci/config.yml on the pushed branch. If the config is missing on that branch, or the project pipelines are disabled, no pipeline is created.

What this error means

Pushes do not trigger pipelines, and the project page indicates pipelines are not set up or the config is disabled.

Your config has been disabled. No .circleci/config.yml found on
branch feature-x. Pipelines will not run until a config is committed.

Common causes

Config not committed on the branch

The .circleci/config.yml exists locally or on another branch but not on the pushed branch.

Project pipelines disabled

The project was unfollowed or pipelines were turned off in project settings.

How to fix it

Commit the config to the branch

Add and commit .circleci/config.yml so the pushed branch has it.

git add .circleci/config.yml
git commit -m "Add CircleCI config"
git push origin feature-x

Re-enable the project

1. Open the project in the CircleCI app.
2. Follow the project and enable pipelines if disabled.
3. Push a commit to confirm a pipeline triggers.

How to prevent it

• Keep .circleci/config.yml committed on all active branches.
• Confirm pipelines are enabled for the project.
• Validate the config before pushing to avoid silent disablement.

Frequently asked questions

Related guides

References

• GitHub Actions documentation