Sync Issues: consolidate workflow using local action

[svg153]

Esta PR consolida el workflow que sincroniza Issues a public/data/issues.json:\n\n- Usa Node 20 y hace npm ci en actions/sync-issue\n- Ejecuta la acción local actions/sync-issue para transformar el Issue en JSON\n- Solo hace commit si public/data/issues.json cambia\n- Replica el archivo a la rama gh-pages cuando hay cambios\n\nRazón: eliminar fragmentos duplicados y asegurar un flujo mínimo y predecible.

[Copilot]

Pull Request Overview

This PR consolidates the workflow that syncs GitHub Issues to public/data/issues.json by:

• Upgrading to Node 20 and using a local action for issue synchronization
• Adding conditional execution to only commit when the data file actually changes
• Streamlining the git operations for both main and gh-pages branches

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The addition of 'labeled' and 'reopened' trigger types is undocumented in the PR description. Consider documenting why these triggers were added to help future maintainers understand the complete scope of issue events that trigger synchronization.

Suggested change

	issues:
	issues:
	# The workflow is triggered on multiple issue events to ensure the JSON data stays in sync.
	# 'labeled' is included to capture changes in issue labels, which may affect downstream processing.
	# 'reopened' is included to handle issues that are reopened, ensuring their state is updated in the JSON.
	# Other events ('opened', 'edited', 'closed') are standard for issue lifecycle changes.

[Copilot]

The || true on line 68 silently ignores fetch errors, which could mask legitimate issues like network failures or repository access problems. Consider checking if gh-pages exists first with git ls-remote --heads origin gh-pages and handling the branch creation case explicitly rather than suppressing all errors.

Suggested change

	git fetch origin gh-pages || true
	git checkout gh-pages || git switch -c gh-pages
	if git ls-remote --exit-code --heads origin gh-pages; then
	git fetch origin gh-pages
	git checkout gh-pages
	else
	git switch --create gh-pages
	fi

[svg153]

He eliminado el fichero scripts/sync-issue.js porque su funcionalidad quedó cubierta por la action local actions/sync-issue y la lógica principal se centralizó en actions/sync-issue/lib/core.js. Mantener ambos generaba duplicación y riesgo de divergencia. Si prefieres conservar una CLI ligera, podemos añadir un script mínimo que invoque las funciones del core, pero el archivo anterior era una copia funcional redundante.

[svg153]

.