Pyasma commented on issue #62500: URL: https://github.com/apache/airflow/issues/62500#issuecomment-4028556758
That’s an interesting approach. One thing I’m wondering about is whether introducing a separate YAML workflow specification might add another layer that needs to be maintained alongside the contributing docs. Since we already agreed that the contributing guides should be the source of truth, another possibility could be to keep the workflow structure directly inside the documentation and extract the actionable parts (commands, fallbacks, environment transitions) using lightweight markers or structured sections. In that model the docs remain both human-readable and the canonical workflow description, while a generator script can derive the agent skill definitions from those sections. This might avoid maintaining a separate workflow specification while still giving agents a deterministic structure to follow. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
