Sorry, I think you misunderstood, and I probably wasn’t very clear.
I have never used 1.0 either however what I found out was that after I added a
.circleci/config.yml into one branch and pushed it. All branches started building, my one with the 2.0 config and then all other pushes into the other branches that had zero circleci configuration still triggered 1.0 builds. I’m pretty sure that I had no filtering on the first config file that I pushed and this may have caused this behaviour. I’m just thinking that maybe this is causing what you mentioned above:
If you check the UI where you can see all the job across all your branches, on the right you’ll see either a 2.0 or 1.0 there. I’m thinking it just may provide insight into why the other branches are building without a config file in them, if you’ve hit the same issue as I did. Oh, and BTW there was no fix. I was told by support that it will stop being an issue when you can no longer perform 1.0 builds after 31st August. In the meantime, I was told that I need to put a 2.0 config file into the branch.