Skip to content

ci(docs): auto-publish TypeDoc API reference to gh-pages#72

Open
bashir1738 wants to merge 8 commits into
Miracle656:mainfrom
bashir1738:ci/typedoc-publish
Open

ci(docs): auto-publish TypeDoc API reference to gh-pages#72
bashir1738 wants to merge 8 commits into
Miracle656:mainfrom
bashir1738:ci/typedoc-publish

Conversation

@bashir1738

Copy link
Copy Markdown
Contributor

Closes #62

Summary

Related issue

Type of change

  • Bug fix
  • New feature
  • Refactor
  • Docs
  • Tests
  • CI / tooling

Checklist

  • I have read CONTRIBUTING.md
  • npx tsc --noEmit passes
  • npm run build passes
  • I added / updated tests where relevant
  • I updated docs where relevant

@Miracle656 Miracle656 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR title and Closes #62 claim TypeDoc auto-publish to gh-pages, but the actual diff is only:

Dockerfile  : 1 line of trailing whitespace
openapi.yaml: 1 line of trailing whitespace

No .github/workflows/typedoc.yml, no typedoc.json, no entry-point config, no gh-pages publish step. I think the branch you pushed doesn't contain the work — the typedoc files are likely staged in a different branch or stashed locally. Could you git status to confirm where the TypeDoc commits ended up, then git push them here?

Once the actual TypeDoc workflow + config land, this will close #62. Until then I can't merge — there's nothing wired up. Also worth reverting the two whitespace changes since they're noise.

@Miracle656 Miracle656 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR, but the diff here doesn't implement what the title/#62 describes. The only change in both files is trailing whitespace added to two lines (the CMD line in the Dockerfile and type: object in openapi.yaml) — there's no TypeDoc generation step and no gh-pages publish workflow.

To close #62 this PR needs to actually:

  • add a typedoc dev-dependency + a script that generates the API reference from the TypeScript sources, and
  • add a GitHub Actions workflow that runs it on push to main and publishes the output to the gh-pages branch (e.g. via peaceiris/actions-gh-pages).

Please also revert the stray trailing-whitespace edits. Happy to re-review once the actual TypeDoc publishing is in place.

bashir1738 and others added 7 commits June 3, 2026 17:21
…ded testPathIgnorePatterns to exclude integration and chaos tests from Jest. - Updated the transform configuration for ts-jest for better readability. - Added vitest as a new dependency for testing. - Removed duplicate fast-check dependency. test: improve opa.test.ts to handle OPA requests more robustly - Changed opaRequestSpy declaration from let to var to avoid ReferenceError due to hoisting. - Enhanced the mock implementation of opaRequestSpy to correctly pass through non-OPA requests. - Updated the test for OPA unreachable scenario to ensure proper handling of supertest connections.
…eady chore: refine chaos test configuration by moving transform settings under the appropriate key
@Miracle656

Copy link
Copy Markdown
Owner

Friendly nudge — the TypeDoc → gh-pages auto-publish is welcome. Please rebase and address the earlier review.

If you're still up for it, please rebase on the latest main and address the review by 2026-07-01 — otherwise I'll close this to keep the queue tidy (you can always reopen). Thanks for contributing! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Auto-publish TypeDoc to gh-pages

2 participants