baseRelDir cannot be set to false in new netlify sites or change to true from older sites

[kaovilai]

Describe the bug

baseRelDIr is not settable by end users of netlify causing new forks of a site created prior to 2019 to never be compatible with netlify.toml in the base directory.

Steps to reproduce

create new site from fork

Configuration

No response

Deploy logs

https://github.com/vmware-tanzu/velero/pull/6981#issuecomment-1771415424

[kaovilai]

oh and I tried to use the answer forums btw.. it's not letting me link github links.. https://answers.netlify.com/t/deploy-did-not-succeed-deploy-directory-site-site-public-does-not-exist/103160/8?u=kaovilai

https://answers.netlify.com/t/basereldir-cannot-be-set-to-false-in-new-netlify-sites-or-change-to-true-from-older-sites/104777

[kaovilai]

linking to github is promotional content wow

[biruwon]

Can you try re-linking the repository to solve it for the old site? You can unlink and then link it again

[kaovilai]

It would be preferable if new contributors are able to contribute without causing old site to make a change ideally.

What do you have against making it configurable?

Or even just have a "migrate to new behavior" button which create pull request and/or update UI settings to new relative dir behavior.

[kaovilai]

Can you try re-linking the repository to solve it for the old site? You can unlink and then link it again

Do you know if this would be enough to trigger the change?