⌘K
Dominik Koch Meet Brandon a bit ago in SF, hes been cooking with toolwind. I really love what you did here Brandon!
Pauline P. Narvas This looks like a great initiative for the Tailwind CSS community! Toolwind sounds like it could be a valuable resource for developers looking to discover and evaluate Tailwind plugins more efficiently. Nice badge, btw!
Amy Egan Hey Eric, I don't think the docs have automatic language translation. At least I'm not aware of it being a feature, and the docs aren't automatically translated for me when I switch my browser language. Do you have a browser extension or setting that might be automatically translating things for you?
Eric Burel Well my bad if it’s not on Vercel side actually! I’ve noticed that automated translation kicks in more and more in various application so the culprit might be Google Chrome actually. I can’t reproduce systematically, so I’ll try to figure what’s going on more precisely. I wonder if there are ways to prevent these automated localization from the website standpoint though (like forcing to respect the language indicated in the html tags etc. ?), they tend to lead to a terrible user experience in the end. There is this idea that LLMs did solve the problem of automated translation but we are quite far from that.
Anshuman Bhardwaj Hi @gochevvo-4216, can you share the date/time when you referred and they accepted? Also, how many referrals have you done this month? Because we have $200 cap on the monthly referrals.
Gochevvo Gmailcom 1 registrated already 2-3 would do this soon yesterday
Gochevvo Gmailcom where my gifted credits?
Pauline P. Narvas This definitely sounds like a caching issue with the Active Branches list in the dashboard. Those URLs *should* update to match the latest deployment for each branch. A couple things you can try: * **Hard refresh the dashboard**: Try Ctrl+F5 (or Cmd+Shift+R on Mac) to fully reload the page. * **See if it keeps happening**: Deploy another branch and check whether the same thing happens again. * **Double-check the deployments**: Head to the **Deployments** tab and make sure each branch really does have its own, distinct deployment URL. Let us know how you get on!
Bastien Limbour Thank you for your quick response. I tried creating a new branch and deploying it with the Vercel CLI in my GitHub Action, but the same issue persists. I have tried the following: * Clearing the browser cache and cookies * Hard-refreshing the dashboard with Cmd+Shift+R * Signing out and back into my Vercel account * Hard-refreshing the dashboard again All the URLs in the Active Branches table remain outdated except for the most recent one. I double-checked the **Deployments** tab: all URLs there are correct and point to the right environment/branch. However, the URLs shown in the **Active Branches** table on the Dashboard remain outdated (even the main production branch still shows an old URL that is no longer used on Vercel).
Amy Egan Yes, Vercel deployment environments are case-sensitive in CLI and programmatic contexts. The built-in environments should be referenced as: * `production` (lowercase) * `preview` (lowercase) * `development` (lowercase) The CLI expects lowercase environment names even though the Vercel Dashboard might display them with capitalization for UI appearance. For custom environments you create, they should also be referenced exactly as you named them with the same case sensitivity
Sangeeth Sudheer Thanks for the response, I’ll keep this in mind for our workflows/scripts. But I wish Vercel app would sync environments then to GitHub under the same name used in programmatic contexts. I set up a new project couple hours back and I see the following on GitHub: I get that GitHub envs are case-insensitive as per docs but still, would’ve been nice if this was consistently managed.
