Skip to content

Add Godot 4 GDScript 2.0 instructions - #5151

Open
otctrading101 wants to merge 1 commit into
github:mainfrom
otctrading101:add-godot-4-gdscript-instructions
Open

otctrading101 wants to merge 1 commit into
github:mainfrom
otctrading101:add-godot-4-gdscript-instructions

Conversation

@otctrading101

Copy link
Copy Markdown

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • I have read and followed the Guidance for submissions involving paid services.
  • My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot.
  • I have run npm start and verified that README.md is up to date.
  • I am targeting the main branch for this pull request.

Description

Adds instructions/godot-4-gdscript.instructions.md (applyTo: "**/*.gd").

Copilot often writes Godot 3 GDScript inside Godot 4 projects, because most tutorials online still use the old syntax. That code doesn't parse in Godot 4. This file gives the Godot 3 -> Godot 4 mapping for the usual offenders:

  • yield(...) -> await
  • export / onready / tool -> @export / @onready / @tool
  • setget -> inline set(value): / get: blocks
  • puppet / remote / remotesync / puppetsync / master -> @rpc(...)
  • connect("signal", self, "method") -> signal.connect(callable), emit_signal() -> signal.emit()
  • funcref -> Callable, Pool*Array -> Packed*Array

It also covers static typing, super() in lifecycle overrides, and StringName / NodePath literals. I checked the mappings against Godot's "Upgrading from Godot 3 to Godot 4" guide and the engine's renames_map_3_to_4.cpp. No existing instruction file covers Godot or GDScript.

docs/README.instructions.md was regenerated with npm start.


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • New agentic workflow.
  • New canvas extension.
  • Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
  • Other (please specify):

Additional Notes

The content is adapted from the MIT-licensed rules I maintain at https://github.com/otctrading101/shiprules-free. The file itself has no links, and it doesn't depend on any paid service.


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

@github-actions

Copy link
Copy Markdown
Contributor

🚦 Submission status: ⏳ Awaiting automation

Risk tier: merge-risk:medium — New or substantially changed resource without privileged execution
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access.

Why this tier
  • Adds 1 file(s), e.g. instructions/godot-4-gdscript.instructions.md

Automated checks

Check Status Details
Line endings 🔧 Infrastructure failure Waiting for a maintainer to approve workflow runs for this PR · logs
Spelling 🔧 Infrastructure failure Waiting for a maintainer to approve workflow runs for this PR · logs
Generated README consistency 🔧 Infrastructure failure Waiting for a maintainer to approve workflow runs for this PR · logs
Risk scan 🔧 Infrastructure failure Waiting for a maintainer to approve workflow runs for this PR · logs
Contributor reputation 🔧 Infrastructure failure Waiting for a maintainer to approve workflow runs for this PR · logs
Duplicate resource scan ⚠️ Failed (advisory, non-blocking) Waiting for a maintainer to approve workflow runs for this PR · logs
PR quality signal ⚠️ Failed (advisory, non-blocking) Waiting for a maintainer to approve workflow runs for this PR · logs

Action needed

  • 🔧 Line endings, Spelling, Generated README consistency, Risk scan, Contributor reputation hit an automation problem that is not caused by your contribution. Comment /rerun-checks to retry; maintainers are notified if it keeps failing.
  • ⚠️ Advisory checks did not complete (Duplicate resource scan, PR quality signal). This does not block the PR.

Review

  • Approvals: 0/1
  • Assigned reviewer: not assigned yet — comment /request-review to ask for one
  • Review target date: not set
  • Still needed: 1 more approval(s)
  • No staffed reviewer pool owns these files yet; any reviewer with write access counts as the domain reviewer.

Commands

Command Who What it does
/rerun-checks PR author, maintainers Re-runs failed or incomplete checks and re-evaluates this gate
/request-review PR author, maintainers Asks the review rotation to assign a reviewer (adds needs-reviewer)

Updated for ae02c90 · gate run · This comment is maintained automatically — see submission gate docs.

This branch has not been deployed

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant