Knut Melvær

Would `--schemaId` be more intuitive? It's not the “builder” that you're IDing. And folk's mental model here is that they have a "schema" they want to add to the studio?

Thanks for the feature request @mshick. This seems like a reasonable request and something that we should consider fixing. Stay tuned!

@benderillo and @am79041: I sense some frustration on both sides in your interaction above here. While we’re trying to figure out what’s going on and hopefully be able to help,...

I believe you can set `working-directory` where you specify the job. So: ```yaml name: Deploy Sanity on: push: branches: [main] jobs: sanity-deploy: defaults: run: working-directory: studio runs-on: ubuntu-18.04 name: Deploy...

I'm on Ruby 2.0.0p247 > On 17. mars 2014, at 06:50, Brett Terpstra [email protected] wrote: > > It should handle those, what version of Ruby are you on? > >...

It seems to me that some data for the `brand` is missing in Theme.js? Can you try adding it and publishing in the Studio, and see if that solves it?

> @kmelve FYI I've disabled the vercel build for now under "settings -> git -> ignored-build-step". Feel free to reenable it for this branch again. Sounds good! I didn't anticipate...

@skovhus and others who land here: We have open-sourced our fork that fixes a lot of these things. It's a stop gap for us as we're migrating out of SC/css-in-js,...

@bjoerge Thanks for the feedback, and shame on me for not properly reviewing AI vibe code. But I have done a bit of refactoring. * The changelog entry is supposed...

> @kmelve could you do a rebase against next and update the PR title so it matches semantic release? 🙏 ref: https://github.com/sanity-io/sanity/actions/runs/13712597273/job/38351775490?pr=8826 > > I think the other CI failures...