Converting the Engine Versioning Workflow over to a sig-content workflow

o3de / sig-content

8 stars 12 forks source link

Converting the Engine Versioning Workflow over to a sig-content workflow #137

Closed FuzzyCarter closed 1 year ago

FuzzyCarter commented 1 year ago

Converting the existing test workflows into an MD workflow for sig-content.

LB-KacperKapusta commented 1 year ago

The Workflow has been completed without new issues being found. It's well written and easy to follow. One suggestion would be informing that <EngineVersion> from Example Parameters in Area: Engine Versioning CLI Workflows has to be an registered Engine's name to work correctly because it might be confusing.

michleza commented 1 year ago

Looked over this today. LGTM!