[ci] Convert GitHub Actions files to new format #18359
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GitHub.com is changing the supported configuration file format for its "Actions" feature [1]. Update to the new format. This change set was produced using the tooling provided by GitHub.com [2]. [1] > The documentation at https://developer.github.com/actions and > support for the HCL syntax in GitHub Actions will be deprecated on > September 30, 2019. Documentation for the new limited public beta > using the YAML syntax is available on https://help.github.com. See > "Automating your workflow with GitHub Actions" for documentation > using the YAML syntax. https://developer.github.com/actions/ [2] https://github.com/actions/migrate
|
There are no reviewers for this pull request. Please reach out on W3C's irc server (irc.w3.org, port 6665) on channel #testing (web client) to get help with this. Thank you! |
|
We'll need to opt in to GitHub's new system before GitHub will recognize the files introduced by this patch:
Limited testing in the |
jgraham
approved these changes
Aug 12, 2019
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Aug 12, 2019
Previously, we identified a problem when attempting to run a GitHub Action for the "pull_request" event when the underlying branch had been deleted [1]. By migrating to the latest GitHub Action beta release [2], we've since gained more insight into the process and more control over its behavior. Alter the configuration for the new "checkout" Step to consistently check out the `master` branch. Update the Action specifier to reference a stable release of the Action. [1] web-platform-tests#18286 [2] web-platform-tests#18359
jugglinmike
added a commit
that referenced
this pull request
Aug 20, 2019
* [ci] Check out master when managing tags & labels Previously, we identified a problem when attempting to run a GitHub Action for the "pull_request" event when the underlying branch had been deleted [1]. By migrating to the latest GitHub Action beta release [2], we've since gained more insight into the process and more control over its behavior. Alter the configuration for the new "checkout" Step to consistently check out the `master` branch. Update the Action specifier to reference a stable release of the Action. [1] #18286 [2] #18359 * fixup! [ci] Check out master when managing tags & labels
natechapin
pushed a commit
to natechapin/wpt
that referenced
this pull request
Aug 23, 2019
…#18393) * [ci] Check out master when managing tags & labels Previously, we identified a problem when attempting to run a GitHub Action for the "pull_request" event when the underlying branch had been deleted [1]. By migrating to the latest GitHub Action beta release [2], we've since gained more insight into the process and more control over its behavior. Alter the configuration for the new "checkout" Step to consistently check out the `master` branch. Update the Action specifier to reference a stable release of the Action. [1] web-platform-tests#18286 [2] web-platform-tests#18359 * fixup! [ci] Check out master when managing tags & labels
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this pull request
Aug 27, 2019
… & labels, a=testonly Automatic update from web-platform-tests [ci] Check out master when managing tags & labels (#18393) * [ci] Check out master when managing tags & labels Previously, we identified a problem when attempting to run a GitHub Action for the "pull_request" event when the underlying branch had been deleted [1]. By migrating to the latest GitHub Action beta release [2], we've since gained more insight into the process and more control over its behavior. Alter the configuration for the new "checkout" Step to consistently check out the `master` branch. Update the Action specifier to reference a stable release of the Action. [1] web-platform-tests/wpt#18286 [2] web-platform-tests/wpt#18359 * fixup! [ci] Check out master when managing tags & labels -- wpt-commits: 6e9bf9411482aa2d931c005ad66750414b6a5fee wpt-pr: 18393
xeonchen
pushed a commit
to xeonchen/gecko
that referenced
this pull request
Aug 27, 2019
… & labels, a=testonly Automatic update from web-platform-tests [ci] Check out master when managing tags & labels (#18393) * [ci] Check out master when managing tags & labels Previously, we identified a problem when attempting to run a GitHub Action for the "pull_request" event when the underlying branch had been deleted [1]. By migrating to the latest GitHub Action beta release [2], we've since gained more insight into the process and more control over its behavior. Alter the configuration for the new "checkout" Step to consistently check out the `master` branch. Update the Action specifier to reference a stable release of the Action. [1] web-platform-tests/wpt#18286 [2] web-platform-tests/wpt#18359 * fixup! [ci] Check out master when managing tags & labels -- wpt-commits: 6e9bf9411482aa2d931c005ad66750414b6a5fee wpt-pr: 18393
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-comments-removed
that referenced
this pull request
Oct 4, 2019
… & labels, a=testonly Automatic update from web-platform-tests [ci] Check out master when managing tags & labels (#18393) * [ci] Check out master when managing tags & labels Previously, we identified a problem when attempting to run a GitHub Action for the "pull_request" event when the underlying branch had been deleted [1]. By migrating to the latest GitHub Action beta release [2], we've since gained more insight into the process and more control over its behavior. Alter the configuration for the new "checkout" Step to consistently check out the `master` branch. Update the Action specifier to reference a stable release of the Action. [1] web-platform-tests/wpt#18286 [2] web-platform-tests/wpt#18359 * fixup! [ci] Check out master when managing tags & labels -- wpt-commits: 6e9bf9411482aa2d931c005ad66750414b6a5fee wpt-pr: 18393 UltraBlame original commit: c883a9dca1672326ff0b5e8cdc47ae41b86fe535
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified
that referenced
this pull request
Oct 4, 2019
… & labels, a=testonly Automatic update from web-platform-tests [ci] Check out master when managing tags & labels (#18393) * [ci] Check out master when managing tags & labels Previously, we identified a problem when attempting to run a GitHub Action for the "pull_request" event when the underlying branch had been deleted [1]. By migrating to the latest GitHub Action beta release [2], we've since gained more insight into the process and more control over its behavior. Alter the configuration for the new "checkout" Step to consistently check out the `master` branch. Update the Action specifier to reference a stable release of the Action. [1] web-platform-tests/wpt#18286 [2] web-platform-tests/wpt#18359 * fixup! [ci] Check out master when managing tags & labels -- wpt-commits: 6e9bf9411482aa2d931c005ad66750414b6a5fee wpt-pr: 18393 UltraBlame original commit: c883a9dca1672326ff0b5e8cdc47ae41b86fe535
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified-and-comments-removed
that referenced
this pull request
Oct 4, 2019
… & labels, a=testonly Automatic update from web-platform-tests [ci] Check out master when managing tags & labels (#18393) * [ci] Check out master when managing tags & labels Previously, we identified a problem when attempting to run a GitHub Action for the "pull_request" event when the underlying branch had been deleted [1]. By migrating to the latest GitHub Action beta release [2], we've since gained more insight into the process and more control over its behavior. Alter the configuration for the new "checkout" Step to consistently check out the `master` branch. Update the Action specifier to reference a stable release of the Action. [1] web-platform-tests/wpt#18286 [2] web-platform-tests/wpt#18359 * fixup! [ci] Check out master when managing tags & labels -- wpt-commits: 6e9bf9411482aa2d931c005ad66750414b6a5fee wpt-pr: 18393 UltraBlame original commit: c883a9dca1672326ff0b5e8cdc47ae41b86fe535
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GitHub.com is changing the supported configuration file format for its
"Actions" feature [1]. Update to the new format.
This change set was produced using the tooling provided by GitHub.com
[2].
[1] > The documentation at https://developer.github.com/actions and
> support for the HCL syntax in GitHub Actions will be deprecated on
> September 30, 2019. Documentation for the new limited public beta
> using the YAML syntax is available on https://help.github.com. See
> "Automating your workflow with GitHub Actions" for documentation
> using the YAML syntax.
[2] https://github.com/actions/migrate
Although I used GitHub-provided tools to make this change, we should still take care when merging it. I'll be available to support that starting at 11:00 EDT on 2019-08-12.