I afraid there is some misunderstanding here. There is not such thing as hosted appveyor.yml setting. AppVeyour reads settings from appveyor.yml which is in repository before every build. If you have appveyor.yml, it takes over UI, unless you check ignore appveyor.yml or set custom and non-existing YAML file name in UI. Another possible issue is if you chose repository type Git instead of GitHub or BitBucket, because generic Git cannot read individual files from repo. More information is here
What I mean is to reset the UI settings with the updated appveyor.yml so that all the UI settings are replaced by their equivalents in the uploaded yml – the end effect being that if I then attempted to download the appveyor.yml via the UI I would have the same file.
This way when a user wants to update their yml file they can upload their current one, make changes in the UI and the download the yml again.
I think this is a lot safer than making changes in the UI and then cut and pasting the bits into a local yml file (where errors can occur).
Thats a good point. Keeping the UI Settings and the appveyor.yml in the repo in sync is pain at the moment. My scenario is:
1. I want to use the UI to configure everything
2. I want to versioning and maybe distribute / reuse my settings in different repos -> therefore i export the yml and check it in whenever i make changes in the UI
-> thats already a pain, would be good if that could be automated
3. When I want to do a small change in the yml file, i have to do the same change in the UI to keep both in sync, otherwise the change would get lost when I do an Export of the apveyor.yml next time
We understand this. Problem is that some features like Exclude configuration from the matrix or Sharing common configuration between branches, to name a few, are very difficult to be expressed in UI. I mean if you try to keep UI simple and clean. We consider UI a good starting point and assume that for more advanced configuration people will go for YAML. Also please note that use YAML from remote location if you have same configuration for different project and want to avoid duplication.