Update CI Workflow to Accommodate New Changes

[sumire88]

Goal

Update the current CI workflow to handle new changes effectively.

Details

• Any changes made to the upstream repository (daeuniverse/dae) will dispatch the downstream workflow to:

  • Sync changes (HEAD SHA) against the main branch in the upstream repository.
  • Update metadata.json accordingly.

• Changes will not be made directly to the main branch in daeuniverse/flake.nix. Instead:

  • The downstream workflow will create a pull request (PR) containing all changes in the unstable branch.
  • Build tests will be executed as part of the PR process.

• If all tests pass, the auto-merge workflow will be triggered:

  • This workflow will be triggered if all the associated check-runs pass. In other words, I will be triggered if the status of workflow_run is completed for the Eval and Lint workflows.

• Once the PR is successfully merged, the changes will be incorporated into the main branch of the downstream repository.

Action Items

• Update the sync-target branch in trigger_downstream_workflow in the upstream repository. ci(trigger-downstream-flake-sync): update sync-target branch dae#716
• Update the CI workflow to support the outlined process.
• Ensure proper PR creation and build-test execution for changes from the upstream repository.
• Refactor unstable branch or merge changes made to the main branch to the unstable branch.
• Implement and validate the auto-merge workflow. ci(automerge-sync-pr): rework workflow #135

Expected Outcome

A seamless and automated process for syncing and merging changes from the upstream repository into the downstream repository while ensuring all tests pass and minimizing manual intervention.

---

Note

Feel free to provide feedback or suggest any improvements to the workflow.

[dae-prow]

Thanks for opening this issue!