GitHub Actions Migration, Proof of Concept testing

[t-will-gillis]

Overview

To better understand the specific requirements involved in migrating GitHub Actions from the Website repository to an organization-level repository, we will conduct a Proof Of Concept migration using the “Schedule Friday 0700” workflow (aka "Add Update Label Weekly").

Action Items

• Perform a POC test migration
• Report to follow

Resources/Instructions

• Ref GitHub Actions Migration Process Proposal #10

[t-will-gillis]

POC: Workflow Migration

• To understand and validate the processes for migrating a GitHub Actions workflow from the Website repository to an organization-level repository, a proof of concept test migration of the “Schedule Friday 0700” workflow (aka "Add Update Label Weekly") from a personal branch to a mock, organization-level repo is being performed.

• The goals are to:

  • Validate that the migration plan is technically sound and implementable.
  • Confirm that scheduled and manual triggers (e.g., schedule, workflow_dispatch) function correctly after migration.
  • Verify that the workflow can access necessary secrets, permissions, and resources when executed from the organization-level repository.
  • Identify any project-specific variables or repository-scoped references that need to be externalized into a reusable configuration file.
  • Produce a validated example of a working organization-level workflow.
  • Document the results and develop a reusable template and configuration structure to simplify future migrations.

• The scope included:

  • Transferring workflow logic and supporting scripts to the (mock) organization-level repository.
  • Updating repository references, paths, and secrets where necessary.
  • Testing functionality through manual triggers.

[t-will-gillis]

Results and Observations

• Created three test repos:
  • .github fork of HfLA's .github repo
  • maintenance-actions Mock org-level repo MAIN architecture
  • Project-X Mock project repo using the centralized workflow

TBC