Conversation
# Conflicts: # locale/en-us.yaml
| Type [ACTIONABLE]`state branch switch <NAME>`[/RESET] to switch to a different branch. | ||
| err_set_default_branch: | ||
| other: Could not update project field with branch, please manually set the `branch={{.V0}}` query parameter on the project field in your activestate.yaml. No newline at end of file | ||
| other: Could not update project field with branch, please manually set the `branch={{.V0}}` query parameter on the project field in your activestate.yaml. |
There was a problem hiding this comment.
nit:
| other: Could not update project field with branch, please manually set the `branch={{.V0}}` query parameter on the project field in your activestate.yaml. | |
| other: Could not update project field with branch. Please manually set the `branch={{.V0}}` query parameter on the project field in your activestate.yaml. |
|
This PR uses the term "detached", but the URL uses "headless". If these two terms are surely the same, I suggest using only one of them across user-facing content. |
|
Will take a look in the morning tomorrow! |
Fwiw this is on purpose since so far the internal lingo has been "headless" and to my knowledge we've had no external lingo. Imo "detached" makes more sense for users. Agree it would be nice if internal and external lingo matched. |
|
Here's a take on the copy, I'll get Pete to take a look at it as well. I think we should indicate what a detached state is & indicate why creating a project is useful. Let me know your thoughts, I'll run through it with @rawktron in our stand as well. Not particularly hot on cc @Naatan |
Yeah, to the cloud is weird. Can we just say "the platform" instead of "the cloud"? You have a double "Visit" in there. Also use a colon and no ellipsis. Also double Is there a place to just edit this copy directly? |
# Conflicts: # changelog.md # locale/en-us.yaml
Added headless state notifications

https://www.pivotaltracker.com/story/show/176809621
Message is a placeholder, product and Luke should review: