Skip to content

Conversation

@overcut-ai
Copy link

@overcut-ai overcut-ai bot commented Jan 8, 2026

Summary

Adds the newly generated AGENTS.md guide so future AI contributors understand the repository layout, tooling, and contribution expectations.

Changes

  • Introduce a comprehensive project overview and repository map
  • Document development scripts, quality gates, and workflow requirements
  • Provide reference examples and key resources for rapid onboarding

Summary

This PR introduces a dedicated `AGENTS.md` guide to onboard AI contributors working in `@amplication/opentelemetry-nestjs`. The document details the repository layout, tooling expectations, coding standards, and reference workflows so agents can contribute consistently.

Changes

  • Documentation: Added `AGENTS.md` with a project overview, repository map, development scripts, and workflow requirements.
  • Documentation: Documented code patterns, quality gates, critical contribution rules, and reference examples to accelerate agent ramp-up.

Commits

Testing

  • Review `AGENTS.md` for accuracy against the current repository structure, tooling, and workflows.
  • Open `AGENTS.md` in GitHub’s markdown preview to ensure formatting, code blocks, and links render correctly.

@overcut-ai
Copy link
Author

overcut-ai bot commented Jan 8, 2026

Completed Working on "Auto PR Description"

✅ Workflow completed successfully.


👉 View complete log

@overcut-ai
Copy link
Author

overcut-ai bot commented Jan 8, 2026

Completed Working on "Code Review"

✅ Workflow completed successfully.


👉 View complete log

Copy link
Author

@overcut-ai overcut-ai bot left a comment

Choose a reason for hiding this comment

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

Review summary

  • Findings: 0 BLOCKER / 0 CRITICAL / 1 MAJOR / 0 MINOR / 0 SUGGESTION / 0 PRAISE
  • Key theme: The AGENTS.md updates misrepresent the releaseBeta.yml workflow as running the full lint → test → build → semantic-release pipeline even though the actual automation only bumps the version and performs npm publish --tag beta.
  • Next steps: Update AGENTS.md to explain that releaseBeta.yml is a manual npm publish flow, call out the exact steps it performs, and describe any lint/test/build gates that must be run manually before triggering it.

Once the documentation accurately reflects the existing beta workflow (or the workflow is updated to match the description), this PR should be ready to merge.

- `tsconfig.build.json` excludes `*.spec.ts` to keep published package clean.
- **Workflow awareness:**
- `ci.yml` enforces install → lint → test:cov → build.
- `release.yml` / `releaseBeta.yml` drive semantic-release jobs; local releases should mimic their command sequences.
Copy link
Author

Choose a reason for hiding this comment

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

[MAJOR]: Lines 42-43/55/92/99 describe releaseBeta.yml as a semantic-release pipeline that mirrors the lint → test → build gates, but the actual workflow (releaseBeta.yml) only bumps the version and runs npm publish --tag beta with no lint/test/build or semantic-release step. This misguides contributors about the validations performed before a beta publish.

Suggested fix: Document that releaseBeta.yml is a manual npm publish flow (version bump + npm publish) and explicitly call out any local lint/test/build steps that must be run manually before invoking it.

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