Erez Rokah

> @erezrokah Could you tell me where should those newly created options be stored? Hi @AbdallahAbis, well I'm not sure. See https://github.com/netlify/netlify-cms/issues/3821#issuecomment-647410593 and https://github.com/netlify/netlify-cms/issues/3821#issuecomment-647547887. The additional options can be saved...

> @erezrokah Why can't we extend the widget options and pass it the additional options by updating `config.yaml`? Hi @AbdallahAbis, updating the `config.yml` means committing it back to GitHub (either...

> * Let's say we have a collection of `articles` > * We have a field of `tags` on that article which is a `list` widget and can be either...

> Will those added values be available to all entries? No they won't. I think I'm start to understand your suggestion. You would like to query all entries (in the...

Hi @AbdallahAbis, please consider you can have multiple select widgets in multiples collections and also nested ones in lists/objects. This means we'll have to read all entries from all collections...

No noob questions - do you have this button when you open the action? 

Regardless, I invited you to collaborate on the repo, long overdue ❤️

Can you try clicking the details button directly?  That should take you to the [specific run](https://github.com/netlify/netlify-cms/runs/3868530666?check_suite_focus=true)

>@erezrokah I'm so sorry for dropping the ball on this. Do you still need this issue to be worked on? I can get back to it in a few days....

Thank for you opening this request @antoineclarose. The CMS UI has been very much about hiding git specifics from editors/users (some backends are not even git based like the test...