You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if create-github-actions-setup-for-ember-addon can update a GitHub Actions workflow created in a previous run.
One way to do so would be storing the configuration used to generate the CI workflow. create-github-actions-setup-for-ember-addon has a configuration interface, which describes the configuration object used to create the CI workflow template:
The parser for TravisCI configuration returns the extracted configuration in that format. The default configuration if no TravisCI configuration also uses that format.
The configuration object used to generate a workflow could be stored at top of the generated CI workflow. It should be stored as a YAML comment to not conflict with the workflow definition itself. It should be stored in a human readable format like YAML. Maybe it's just an outcommented YAML?
# This file has been generated by `yarn create github-actions-setup-for-ember-addon`# using the following configuration:## browsers:# - chrome# emberTryScenarios:# allowedToFail:# - ember-beta# - ember-canary# required:# - ember-lts-3.20# - ember-release# nodeVersion: 10# packageManager: yarn## Running `yarn create github-actions-setup-for-ember-addon` again will update the# CI workflow to the latest blueprint.
We would than implement a parser similar to the parser for TravisCI configuration, which looks for a .github/workflows/ci.yml and extract the information from previous run out of it.
Maybe we want to store a version together with the configuration object if we want to ship a breaking change in that configuration object.
The text was updated successfully, but these errors were encountered:
It would be great if
create-github-actions-setup-for-ember-addon
can update a GitHub Actions workflow created in a previous run.One way to do so would be storing the configuration used to generate the CI workflow.
create-github-actions-setup-for-ember-addon
has a configuration interface, which describes the configuration object used to create the CI workflow template:create-github-actions-setup-for-ember-addon/src/index.ts
Lines 8 to 16 in a95d213
The parser for TravisCI configuration returns the extracted configuration in that format. The default configuration if no TravisCI configuration also uses that format.
The configuration object used to generate a workflow could be stored at top of the generated CI workflow. It should be stored as a YAML comment to not conflict with the workflow definition itself. It should be stored in a human readable format like YAML. Maybe it's just an outcommented YAML?
We would than implement a parser similar to the parser for TravisCI configuration, which looks for a
.github/workflows/ci.yml
and extract the information from previous run out of it.Maybe we want to store a version together with the configuration object if we want to ship a breaking change in that configuration object.
The text was updated successfully, but these errors were encountered: