Skip to content

Conversation

@zardus
Copy link
Member

@zardus zardus commented Nov 19, 2025

No description provided.

@zardus
Copy link
Member Author

zardus commented Nov 19, 2025

@ConnorNelson

@github-actions github-actions bot added the dangerous Changes critical or security-sensitive files label Nov 19, 2025
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@@ -0,0 +1 @@
{% extends "common/run.j2" %}

Choose a reason for hiding this comment

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

P1 Badge Name Jinja run scripts with .j2 extension

The run entrypoint for level‑11 is just the Jinja directive {% extends "common/run.j2" %} but the file is named run instead of run.j2. Per the repo’s guidance only .j2 files are rendered, so this file (and the similar run files in levels 12–14) will be copied verbatim and Python will hit a SyntaxError on the {% … %} line when the challenge starts. These challenges will not run at all unless the run templates are rendered.

Useful? React with 👍 / 👎.

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

Labels

dangerous Changes critical or security-sensitive files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants