Skip to content

13: Leave one repository a newcomer can pick up - #20

Open
CptSchnitz wants to merge 5 commits into
migration/12-e2e-lintfrom
migration/13-housekeeping
Open

13: Leave one repository a newcomer can pick up#20
CptSchnitz wants to merge 5 commits into
migration/12-e2e-lintfrom
migration/13-housekeeping

Conversation

@CptSchnitz

@CptSchnitz CptSchnitz commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator

Layer 13 of 13, based on migration/12-e2e-lint. Ticket: .scratch/monorepo-migration/issues/13-housekeeping.md (now removed by this PR — see below).

What this does

  • One command for a newcomer. pnpm install && pnpm verify lints, formats, type-checks, builds and tests every workspace (turbo run format lint type-check build test). e2e is deliberately excluded — it needs Docker and runs on its own (pnpm e2e). README rewritten to describe the workspace layout and this command.
  • One dependency-update configuration. .github/dependabot.yml replaces the three former per-repository Dependabot configs, using the new directories glob support to cover the root and every app/package/e2e in one block.
  • Documentation generation covers the SDK only. Root typedoc.json (packages mode, entry point packages/jobnik-sdk only) + the SDK's own typedoc.json + a GitHub Pages deploy workflow scoped to SDK changes. Output goes to docs/sdk, not docs, since the repo root's docs/ already holds the agent-skill domain docs.
  • Former-repository leftovers removed. e2e's README and package.json still pointed a newcomer at the archived jobnik-e2e repository (clone URL, an npm test quick start that doesn't match this workspace's actual e2e script, a link to the separate jobnik-manager repo, and stale repository/bugs/homepage metadata). All of it now points into this monorepo, matching the SDK's existing pattern. Service-catalog descriptors were confirmed already dropped when the workspaces were moved in (layer 2).
  • The migration's own scratch tracker removed. .scratch/monorepo-migration/ (spec, stack conventions, all 13 ticket files) served its purpose; deleted so it doesn't sit around as clutter now that the stack is complete. The .scratch/ convention itself (docs/agents/issue-tracker.md) is untouched — it's generic, for future feature work.
  • Deliberately excluded follow-up work, filed rather than forgotten:

Not in this PR

  • Archiving the three source repositories — a human step, called out as such in the ticket.

Verification

  • pnpm verify passes clean (17/17 tasks).
  • pnpm docs builds SDK docs into docs/sdk without touching docs/agents.
  • Dependabot's new commit prefixes (deps(deps), devdeps(deps), ci(deps)) pass commitlint — checked directly against commitlint.config.js's scope enforcement.

🤖 Generated with Claude Code

@CptSchnitz CptSchnitz changed the title migration/13 housekeeping 13: Leave one repository a newcomer can pick up Aug 24, 2026
@github-actions

github-actions Bot commented Aug 24, 2026

Copy link
Copy Markdown

Coverage Report for apps/jobnik-manager

Status Category Percentage Covered / Total
🟢 Lines 100% (🎯 80%) 750 / 750
🟢 Statements 100% (🎯 80%) 767 / 767
🟢 Functions 100% (🎯 80%) 112 / 112
🟢 Branches 100% (🎯 80%) 219 / 219
File CoverageNo changed files found.
Generated in workflow #18 for commit f5379dc by the Vitest Coverage Report Action

CptSchnitz and others added 5 commits August 26, 2026 11:16
Three per-repository Dependabot configs (manager, SDK, e2e) become one
`.github/dependabot.yml` at the root. The npm entry uses the new
`directories` glob support to cover the root and every app, package and
the e2e suite in one block, so upgrades arrive as a single stream of
pull requests and a new workspace is picked up automatically rather
than needing its own entry.

Commit-message prefixes are updated to satisfy this repo's own scope
enforcement (`commitlint.config.js`): every Dependabot commit now
carries the `deps` scope, which is allowed explicitly for
dependency-bump commits that don't name a single workspace.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Documentation generation covers the SDK only -- the manager's public
interface is its specification, not its source. Mirrors the reference
monorepo's TypeDoc setup: a root `typedoc.json` in "packages" entry
mode pointed only at `packages/jobnik-sdk`, that package's own
`typedoc.json` carrying over its entry point and tsconfig from the
source repository, and a `pnpm docs` script.

Output goes to `docs/sdk`, not `docs`, because the repository root's
`docs/` already holds the agent-skill domain docs (`docs/agents/`) --
pointing TypeDoc at `docs` directly would let its clean-output-dir step
delete them.

The GitHub Pages deploy workflow is carried over from the SDK's former
repository, adapted to this repo's `init-pnpm` action and scoped to
push events touching the SDK or the doc-generation config.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…mand verify

From a fresh clone, `pnpm install && pnpm verify` now lints, formats,
type-checks, builds and tests every workspace -- one turbo invocation
covering the whole task graph, e2e excluded since it needs Docker and
runs on its own. The README replaces its placeholder with the
workspace layout, that command, and where generated docs and
dependency updates now live.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
README and package.json still pointed a newcomer at the archived
jobnik-e2e repository: a clone URL for it, an "npm ci"/"npm test"
quick start (npm scripts that don't even exist here -- this workspace's
task is named "e2e", not "test"), a link to the separate jobnik-manager
repository for local setup, and repository/bugs/homepage metadata for
jobnik-e2e. All of it now points into this monorepo instead, matching
the pattern already used by packages/jobnik-sdk's package.json.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The spec, stack conventions and all 13 ticket files under
.scratch/monorepo-migration/ were the working issue tracker for this
migration. With layer 13 landing, the stack is complete and the
tracker is done serving its purpose -- remove it rather than leave it
as clutter for a newcomer to puzzle over. The .scratch/ convention
itself (docs/agents/issue-tracker.md) is unaffected: it's a generic
mechanism for future feature work, not specific to this migration.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@CptSchnitz
CptSchnitz force-pushed the migration/13-housekeeping branch from 4e920b0 to f5379dc Compare August 26, 2026 08:17

@ronenkapelian ronenkapelian left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

  1. pr title not according to commitlint
  2. container_name: 'postgres-for-testing' - two workspaces hardcode the same Docker container name, will couse collusion on running parallel
    3.add a root .vscode/settings.json
    4.add .gitattributes file (like in opa-la)
    5.add .licrc file

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.

2 participants