Skip to content

Post-merge metadata update (after #15)#16

Closed
github-actions[bot] wants to merge 1 commit intomasterfrom
bot/metadata-post-merge-pr15-20260115-072457
Closed

Post-merge metadata update (after #15)#16
github-actions[bot] wants to merge 1 commit intomasterfrom
bot/metadata-post-merge-pr15-20260115-072457

Conversation

@github-actions
Copy link

Auto-update *.metadata.txt after PR #15 merged.

@weasel-lee
Copy link
Owner

@codex

METADATA_POST_MERGE_JOB_V1

Please update Rust metadata files in this PR (post-merge fixup). Submit the result directly to GitHub (commit) without asking for toggles or confirmations.

Rules:

  • Allowlist: .github/metadata/allowlist.txt (supports !exclude).
  • Output path mapping: /path/to/src/a.rs -> /path/to/src/a.metadata.txt
  • Prompt: follow .github/metadata/prompt.txt exactly.
  • Added Rust file: create metadata from Rust source + prompt.
  • Modified Rust file: update metadata using Rust source + existing metadata + prompt.
  • Deleted Rust file: delete corresponding .metadata.txt if exists.
  • Do not include housekeeping hash headers like "# source_sha256:" in your output.

Targets (from merged diff):
Added:
(none)

Modified:
(none)

Deleted:
(none)

@weasel-lee weasel-lee closed this Jan 15, 2026
@chatgpt-codex-connector
Copy link

Summary

  • No metadata updates were required because the trigger listed no added, modified, or deleted Rust files.

Testing

  • Not run (no changes).

View task →

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.

1 participant