We can troubleshoot a problematic config YML script without having to make Git commits by using the CircleCI API. One technique that we can do is to create another folder and place a duplicate of our config YML script into it and then use this YML script as our debugging script. Once we can verify that the YML script is working correctly we can update the original YML script. This is useful since we won't be clogging up the Git history with troubleshooting commits but instead we will hit the CircleCI API directly.
Logging and troubleshooting techniques
Running a build using a local config YML script to troubleshoot
Let's say that we want to experiment with storing build artifacts, such as code coverage on a project...