Open
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
StellarRounin
commented
Apr 12, 2026
Author
StellarRounin
left a comment
There was a problem hiding this comment.
Resolved all the issues
Author
|
@greptile review |
Comment on lines
5954
to
5955
| }, | ||
| { | ||
| "id": "strapi", | ||
| "name": "Strapi", | ||
| "version": "v5.33.0", | ||
| "description": "Open-source headless CMS to build powerful APIs with built-in content management.", | ||
| "logo": "strapi.svg", | ||
| "links": { | ||
| "github": "https://github.com/strapi/strapi", | ||
| "discord": "https://discord.com/invite/strapi", | ||
| "docs": "https://docs.strapi.io", | ||
| "website": "https://strapi.io" | ||
| }, | ||
| "tags": [ | ||
| "headless", | ||
| "cms", | ||
| "content-management" | ||
| ] | ||
| }, | ||
| { |
There was a problem hiding this comment.
Strapi entry accidentally removed
The diff shows the entire strapi blueprint entry (id, name, version, description, logo, links, tags) deleted from meta.json by this PR. This appears to be a rebase or merge artifact. The Strapi template should still be present between the streamflow and supabase entries — please restore it before merging.
Author
There was a problem hiding this comment.
Strapi is duplicated, it already exists in line 5919
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
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.
What is this PR about?
New PR of Wallabag
This PR:
Screenshots or Videos
Greptile Summary
This PR adds a Wallabag blueprint with previous review issues largely addressed (version, restart policy, relative paths, credentials), but three blocking issues remain. The
template.tomlincorrectly placesDB_PASSWORD,ROOT_PASSWORD, and the missingDOMAINmapping inside[[config.domains]]instead of a[config.env]table, so none of these variables will be substituted indocker-compose.yml. Thewallabag/wallabagimage is unpinned whilemeta.jsondeclares version2.6.14. Finally, the Strapi entry has been accidentally deleted frommeta.json, likely due to a rebase conflict.Confidence Score: 3/5
Not safe to merge — broken env config prevents database auth and domain routing, and Strapi is accidentally deleted from the registry.
Three P1 issues: the env variable misconfiguration in template.toml breaks the primary user path (DB auth fails, domain redirect fails); the wallabag image is unpinned counter to the version declared in meta.json; and the Strapi entry deletion from meta.json is an unintended regression. These need to be resolved before merging.
blueprints/wallabag/template.toml (env variable structure), blueprints/wallabag/docker-compose.yml (pinned image version), meta.json (restore Strapi entry)
Reviews (2): Last reviewed commit: "fix: Delete duplicate strapi from meta j..." | Re-trigger Greptile
Context used: