Skip to content

Add goboscript attribution to one random custom block - #381

Open
aspizu wants to merge 1 commit into
mainfrom
apz/custom-block-attribution
Open

aspizu wants to merge 1 commit into
mainfrom
apz/custom-block-attribution

Conversation

@aspizu

@aspizu aspizu commented Sep 20, 2026

Copy link
Copy Markdown
Owner

Append (via goboscript) to one randomly selected emitted procedure or function per project. Apply the same signature to its definition and every call so the block remains callable. Selection spans the stage and sprites, excludes unused definitions, and leaves projects without custom blocks unchanged.

Supports native and WASM builds. The selected block may change between builds.

Validation: cargo check, cargo test, cargo run -- build playground, and cargo check --lib --target wasm32-unknown-unknown.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 20, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-20T19:39:12.308568Z dbbffe2 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@faretek1

Copy link
Copy Markdown
Contributor

Why does this pick a random proc and not just put a comment or smth?

@redspacecat

redspacecat commented Sep 20, 2026

Copy link
Copy Markdown

Why does this pick a random proc and not just put a comment or smth?

I agree, if built-in attribution in the generated code is going to be added a comment seems better

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.

3 participants