Skip to content

viable/strict: use composite action instead of reusable workflow #8660

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

viable/strict: use composite action instead of reusable workflow #8660

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 11 additions & 8 deletions .github/workflows/update-viablestrict.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,14 @@ concurrency:

jobs:
do_update_viablestrict:
uses: pytorch/test-infra/.github/workflows/update-viablestrict.yml@main
with:
repository: pytorch/vision
required_checks: "Build Linux,Build M1,Build Macos,Build Windows,Tests,CMake,Lint,Docs"
test-infra-ref: main
secrets:
ROCKSET_API_KEY: ${{ secrets.ROCKSET_API_KEY }}
GITHUB_DEPLOY_KEY : ${{ secrets.VISION_GITHUB_DEPLOY_KEY }}
runs-on: ubuntu-20.04
steps:
- name: Update viable/strict
uses: pytorch/test-infra/.github/actions/update-viablestrict@main
with:
repository: pytorch/vision
stable-branch: viable/strict
test-infra-ref: main
requires: '[\"Build Linux\",\"Build M1\",\"Build Macos\",\"Build Windows\",\"Tests\",\"CMake\",\"Lint\",\"Docs\"]'
rockset-api-key: ${{ secrets.ROCKSET_API_KEY }}
secret-bot-token: ${{ secrets.VISION_GITHUB_DEPLOY_KEY }}
Loading