Skip to content

chore: sync development into main - #18

Open
nicomiguelino wants to merge 1 commit into
mainfrom
development
Open

chore: sync development into main#18
nicomiguelino wants to merge 1 commit into
mainfrom
development

Conversation

@nicomiguelino

Copy link
Copy Markdown
Contributor

Syncs the EDGE_APP_ID rollout changes from development into main.

- Set STAGE_EDGE_APP_ID and PRODUCTION_EDGE_APP_ID repo variables and pass them through to the initialize/update actions as edge_app_id
- Drop id from screenly.yml and delete screenly_qc.yml since a single manifest is now used regardless of environment
- Pin edge-apps-actions to a commit for now, since v26.9.0 can't be tagged there until a repo ruleset is adjusted
Copilot AI lite review requested due to automatic review settings September 4, 2026 05:13

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

It changes production deployment workflows and introduces environment-dependent edge_app_id resolution that should be validated against configured secrets/vars and the intended pinned action revision.

Pull request overview

Syncs the EDGE_APP_ID rollout from development into main by shifting Edge App identification out of the committed manifest and into GitHub Actions inputs for stage/production deployments.

Changes:

  • Removed the id field from screenly.yml and deleted the screenly_qc.yml manifest.
  • Pinned Screenly Edge App GitHub Actions to a specific commit SHA instead of the floating v1 tag.
  • Added edge_app_id inputs to deploy/initialize workflows, sourcing from secrets.EDGE_APP_ID with fallbacks to environment vars.
File summaries
File Description
screenly.yml Removes embedded app ID from the manifest.
screenly_qc.yml Removes the QC manifest entirely.
.github/workflows/update-edge-app.yml Pins the update action and injects edge_app_id via secrets/vars for stage and production deploys.
.github/workflows/initialize-edge-app.yml Pins the initialize action and injects edge_app_id based on selected environment.
Review details
  • Files reviewed: 4/4 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

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.

2 participants