Add GitHub Actions workflow to create per-tool data-schema issues

[Copilot]

No GitHub Issues existed to guide tool owners on filling out their placeholder YAML schemas. This adds an automated, idempotent workflow that creates one scoped issue per tool on push to main.

New files

• .github/workflows/create-tool-issues.yml — triggers on push to main (path-filtered to these new files) and workflow_dispatch; requires only issues: write + contents: read
• .github/scripts/create_tool_issues.py — creates/skips issues via gh CLI; checks open issue titles before creating to prevent duplicates
• .gitignore — excludes __pycache__/ and .pyc

Issues created (one per tool)

Covers all 7 tools enumerated from data_schemas/: Sienna Data Model, GenX Data Model, Grid Data Model, CommonEnergySystemModel, PyPSA Data Model, Encoord Data Model, CIM/ENTSO-E.

Each issue body includes:

• Direct link to the tool's YAML file on main
• Direct hyperlink to fill_out_schema.md
• File location + naming convention
• Required-sections table (all 7 YAML sections + key fields)
• yamllint validation command
• PR instructions for both fork-based and branch-based contributors
• 10-item acceptance-criteria checklist

Original prompt

Create GitHub Issues (not PR) for each tool in the repository to guide tool owners on how to add their data schema YAMLs. Each issue should:

• Be created in repo G-PST/data-schema-excercise on branch main.
• Be specific to a single tool (one issue per tool).
• Instruct the tool owner to add their tool’s data schema YAML file(s) according to the instructions in fill_out_schema.md.
• Include a direct hyperlink to fill_out_schema.md in the repository (use a GitHub URL pointing to the file on main).
• Clearly describe the expected deliverables (where to place the YAML, naming conventions if present, required fields, validation steps, and how to open a PR).
• Include acceptance criteria/checklist for the tool owner to confirm completion.

If needed, first enumerate the tools present in the repository (e.g., from directories or manifests) to ensure an issue is created for each tool.

This pull request was created from Copilot chat.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.