Conversation
* api docs structure * CORE: make new docs section work * CORE: make new nav section work * CORE: netlify structure * CORE: todos * CORE: temp disable
Removed the 'ref' option from the Checkout step.
…d improve build process
* Fix docs-graph CMS schema to match nested docs.yml structure. The content file now stores sections under items → children → sections, but production CMS still treated children as flat section rows, leaving id/title/description fields empty in the editor. Co-authored-by: Cursor <cursoragent@cursor.com> * CORE: trigger --------- Co-authored-by: Cursor <cursoragent@cursor.com>
* Fix docs-graph CMS schema to match nested docs.yml structure. The content file now stores sections under items → children → sections, but production CMS still treated children as flat section rows, leaving id/title/description fields empty in the editor. Co-authored-by: Cursor <cursoragent@cursor.com> * CORE: validate email based on domain * CORE: validate improved * CORE: validate links if we dont have domain * CORE: validate message view * CORE: add stg env * CORE: add input field indicator * CORE: add ror name fix --------- Co-authored-by: Cursor <cursoragent@cursor.com>
…for azure-func-backend
… for azure-func-backend
public/design was gitignored, so the icon sprite/svgs only existed on dev machines from a stale manual build; CI checkouts never had them. Removing the "design build icons" step (prior commit) made prod build nothing at all instead. Track the actual assets and let both dev and prod serve the same committed sprite.
…correctly
@oacore/design's postinstall regenerates its config (icon sprite public
path) by reading design.config.js. It ran before COPY . ., so the file
wasn't there yet and the default publicPath ('/') got baked in instead
of '/design', producing <use href="/icons.svg#..."> refs that 404
(actual sprite lives at /design/icons.svg). Copying the config alongside
the lockfiles fixes the reference; COPY . . still overwrites
public/design with the tracked full icon set afterward.
* Fix docs-graph CMS schema to match nested docs.yml structure. The content file now stores sections under items → children → sections, but production CMS still treated children as flat section rows, leaving id/title/description fields empty in the editor. Co-authored-by: Cursor <cursoragent@cursor.com> * CORE: add recaptcha * CORE: add to correct place --------- Co-authored-by: Cursor <cursoragent@cursor.com>
* Fix docs-graph CMS schema to match nested docs.yml structure. The content file now stores sections under items → children → sections, but production CMS still treated children as flat section rows, leaving id/title/description fields empty in the editor. Co-authored-by: Cursor <cursoragent@cursor.com> * CORE: add domain search --------- Co-authored-by: Cursor <cursoragent@cursor.com>
* Fix docs-graph CMS schema to match nested docs.yml structure. The content file now stores sections under items → children → sections, but production CMS still treated children as flat section rows, leaving id/title/description fields empty in the editor. Co-authored-by: Cursor <cursoragent@cursor.com> * CORE: add new logo --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Removed cache-from and cache-to options from Docker build.
Removed cache-from and cache-to arguments from Docker build step.
* Fix docs-graph CMS schema to match nested docs.yml structure. The content file now stores sections under items → children → sections, but production CMS still treated children as flat section rows, leaving id/title/description fields empty in the editor. Co-authored-by: Cursor <cursoragent@cursor.com> * CORE: remove OU * CORE: add test * CORE: add test ოლდ * CORE: remove button --------- Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
* Fix docs-graph CMS schema to match nested docs.yml structure. The content file now stores sections under items → children → sections, but production CMS still treated children as flat section rows, leaving id/title/description fields empty in the editor. Co-authored-by: Cursor <cursoragent@cursor.com> * CORE: update email redirect * CORE: add updated OU --------- Co-authored-by: Cursor <cursoragent@cursor.com>
* Fix docs-graph CMS schema to match nested docs.yml structure. The content file now stores sections under items → children → sections, but production CMS still treated children as flat section rows, leaving id/title/description fields empty in the editor. Co-authored-by: Cursor <cursoragent@cursor.com> * CORE: add updated docs --------- Co-authored-by: Cursor <cursoragent@cursor.com>
* Fix docs-graph CMS schema to match nested docs.yml structure. The content file now stores sections under items → children → sections, but production CMS still treated children as flat section rows, leaving id/title/description fields empty in the editor. Co-authored-by: Cursor <cursoragent@cursor.com> * CORE: add updated logo --------- Co-authored-by: Cursor <cursoragent@cursor.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
4 participants
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.
No description provided.