Weekly data workflow only refreshes an unused file and pushes straight to unprotected main
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 30/100
Rechercherichtung
Start by reading .github/workflows/update-unity-api.yml, .github/scripts/refresh_unity_data.py, and the MCP server references to the JSON data files. Check how the workflow validates and publishes refreshed data, and which files the tools load. Done means data changes arrive in CI-passing PRs, refreshed data is used, and main has the stated protection and lifecycle compatibility behavior; this spans workflow, server, and repository settings.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Why it matters
The weekly "Update Unity API Data" workflow looks like it keeps the API database current, but it only rewrites lifecycle_order.json, which no MCP tool reads. It also pushes directly to an unprotected main, pinned to an old docs version. It gives a false sense of freshness while adding unreviewed commits.
Evidence
.github/scripts/refresh_unity_data.py:118-121- onlylifecycle_order.jsonis refreshed.unity_api_common.json,deprecated_patterns.json,shader_properties.json,platform_defines.jsonare never updated.grep lifecycle_order mcp-server/server.pyreturns nothing: no tool loads that file.refresh_unity_data.py:22-UNITY_DOCS_BASE = ".../6000.1/Documentation/ScriptReference"is hardcoded.- The lifecycle list includes
OnPreCull,OnPreRender,OnPostRender,OnRenderImage, which are not called in URP/HDRP, with no pipeline note. .github/workflows/update-unity-api.ymlcommits andgit pushes straight tomain;gh api .../branches/main/protectionreturns "Branch not protected".
Suggested approach
- Either expose lifecycle data through a tool (e.g. a
lifecycle_infotool or include it inlookup_api) or stop refreshing it. - Rename the workflow to reflect what it does, read the docs version from a single config value, and open a PR (e.g.
peter-evans/create-pull-request) instead of pushing tomain. - Enable branch protection on
mainwith required status checks (Validate), and allow the release bot through a ruleset bypass. - Add a pipeline-compatibility field to lifecycle entries.
Done when
Automated data changes arrive as PRs that pass CI, the refreshed data is actually used, and main is protected.
- Vorherrschende Sprache
- C#
- Sterne
- 4
- Forks
- 0
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus TMHSDigital/Unity-Developer-Tools
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
-
ci priority: low skills
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 55/100
-
good first issue skills testing
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 58/100
-
ci priority: medium testing
Schwierigkeit 4/5 1-2 Tage Anfängerfreundlichkeit 57/100
-
documentation marketing priority: medium
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 35/100
Alle Issues in TMHSDigital/Unity-Developer-Tools
Ähnliche Issues
-
type:task ux
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
elsa-workflows/elsa-foundation#5253 ·
Maintainer antworten meist innerhalb von 1 Tag