# Testing Config Files Locally

**URL:** <https://discuss.circleci.com/t/testing-config-files-locally/27888>\
**Category:** Build Environment\
**Created:** [January 23, 2019, 6:28pm UTC](https://discuss.circleci.com/t/testing-config-files-locally/27888 "2019-01-23T18:28:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![alzadude](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@alzadude](https://discuss.circleci.com/u/alzadude)\
**Post date:** [January 23, 2019, 6:28pm UTC](https://discuss.circleci.com/t/testing-config-files-locally/27888/1 "2019-01-23T18:28:27Z")

</div>

Hi there,

I’m looking to test a locally-modified config.yml to avoid polluting the git log with my attempts, but it seems that both of the documented solutions don’t support workflows:

[https://circleci.com/docs/2.0/examples/#section=configuration](https://circleci.com/docs/2.0/examples/#section=configuration)

[https://circleci.com/docs/2.0/local-cli/](https://circleci.com/docs/2.0/local-cli/)

However, in the API docs I found a new API call: [https://circleci.com/docs/api/#trigger-a-new-build-by-project-preview](https://circleci.com/docs/api/#trigger-a-new-build-by-project-preview)

It states “Workflows will be run or scheduled in the same way as when a webhook from source control is received.” This looks like what I needed!

However, when I make an API call to this endpoint, I get the following error:

“Unexpected parameter(s): :config, :notify”

So it seems this new endpoint doesn’t allow the local config to be included in the POST. Is there any way this could be allowed? Or is there some other way to do what I want?

Thanks!

---

<div class="post-metadata">

**Author:** ![halfer](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/halfer/32/9083_2.png) [@halfer](https://discuss.circleci.com/u/halfer)\
**Post date:** [January 23, 2019, 8:53pm UTC](https://discuss.circleci.com/t/testing-config-files-locally/27888/2 "2019-01-23T20:53:28Z")

</div>

> [@alzadude](#):
>
> I’m looking to test a locally-modified config.yml to avoid polluting the git log with my attempts

It would probably be easier to clone your repo, make as many pushes as you need to get that working, then rebase all your changes into one commit on the main repo.

Or use a branch on the main repo, then throw the branch away after you’ve squashed the changes onto `master` - though that will leave a trail of failed builds in your CI history.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [April 23, 2019, 8:53pm UTC](https://discuss.circleci.com/t/testing-config-files-locally/27888/3 "2019-04-23T20:53:30Z")

</div>

Closed on April 23, 2019, 8:53pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![Benny](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/benny/32/31553_2.png) [@Benny](https://discuss.circleci.com/u/Benny)\
**Post date:** [April 22, 2024, 8:17pm UTC](https://discuss.circleci.com/t/testing-config-files-locally/27888/4 "2024-04-22T20:17:45Z")

</div>

This feature is now available through our VS Code extension: [Introducing the ability to test run config.yml changes from VS Code (Open Preview)](https://discuss.circleci.com/t/introducing-the-ability-to-test-run-config-yml-changes-from-vs-code-open-preview/50394)