Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Feature: Ability to change which branch config.yml is grabbed from
See original GitHub issueIs your feature request related to a problem? Please describe.
When doing development work, there is the problem that NetlifyCMS grabs the config.yml file from the production branch instead of the dev branch. This makes development for the config really hard, as I have to work on the production branch which is meant to be used for the production version of the website.
Describe the solution you’d like
It would be great if CMS grabbed the current branch from the netlify branch deploy. Currently i have netlify make a branch deploy to dev.example.com and a production deploy to example.com. If netlify CMS talked to netlify about what branch it was on, and then grabbed the corresponding config.yml file from the repo this would be much easier.
Another solution may be to have a <meta> tag you can add to the index.html to tell netlify CMS what branch to get the config file from?
Describe alternatives you’ve considered I have considered having another repo for development, but this just adds another layer of difficulty.
Additional context May be related to #770
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Seems the problem was that i hadn’t configured stuff properly. Closing now
Yea, for me i always get the same config.yml. I’ll make a new site now, just to test how it works, and to see if there is a bug on my end