Conversation
…repo — just `README.md` and `mintlify-docs/`). The staged/unstaged changes are only the 3 Mintlify `.mdx` doc updates. The build summary's decorator/spec/RuboCop work (Tour, Survey, Embed decorators, `models_spec` fix) isn't in this repo at all — it must live in a different worktree/repo, likely `edit` (the actual Rails backend with decorators and RSpec). I can't write one commit message covering both; only the docs changes exist here. Nothing is staged in this worktree (`git diff --staged` is empty) — should I stage the three `.mdx` files and write the commit message for just those doc changes, or did you mean to point me at the `edit` worktree for the decorator/spec work?
The schema rows and JSON samples carry the two fields; the added section restated them at length without adding anything a reader needs. Co-authored-by: Chameleon dev <dev@trychameleon.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
scheduled_publish_at/scheduled_unpublish_atCampaign fields on the public REST API's Tour, Survey, and Embed decorators, so integrators can see scheduled unpublish dates without polling the dashboardexpect_response_code(200)in the new models_spec case that was asserted before any request was made🤖 Chameleon dev for CORE-200