FG Forrest
Official@fgforrest · Czech Republic
Offers specialized engineering maintenance and schema evolution services for the evitaDB ecosystem, focusing on contract integrity and release management.
Agent Skills by FG Forrest
Showing 8 vetted skills indexed across 1 GitHub repositories.
FgForrestnew-constraint
Plan end-to-end implementation steps for a new evitaDB query constraint.
FgForrestopenapi-breaking-changes
Compare evitaDB OpenAPI REST schemas to identify breaking changes.
FgForrestevita-schema-change
Apply evitaDB schema changes across contracts, DTOs, builders, mutations, and serializers.
FgForrestrelease-notes
Generate release-notes.md for evitaDB releases from tags, commits, and issues.
FgForrestcode-quality-pipeline
Coordinate planning, execution, and verification in a three-phase code-quality pipeline.
FgForrestnew-external-api-object
Add new API objects across evitaDB external APIs using descriptor inheritance and converters.
FgForrestrelease-pr
Create or update GitHub PRs from dev to master with auto-generated release notes.
FgForrestgql-breaking-changes
Compare GraphQL schemas and report breaking changes between evitaDB demo and local branch.
Frequently Asked Questions About FG Forrest
FAQPage SchemaWhat specific tasks does FG Forrest enable for evitaDB developers?▼
FG Forrest enables precise schema evolution by identifying breaking changes in GraphQL and OpenAPI definitions. It facilitates the propagation of database schema updates across contracts, DTOs, and serializers, while managing the generation of release documentation and pull requests to ensure consistent deployment cycles.
Which technical personas benefit from these capabilities?▼
These capabilities are designed for backend engineers and database administrators working within the evitaDB ecosystem. They are particularly useful for developers managing complex data contracts, ensuring interface stability during iterative development, and maintaining rigorous code quality standards across multi-phase release pipelines.
What are the prerequisites for implementing these schema management tasks?▼
Implementation requires an existing evitaDB project structure with defined OpenAPI or GraphQL schemas. Users must have repository access to manage branch merges and commit history, as the functionality relies on comparing local branch states against established demo or master schemas to detect breaking changes.