Fixed the typo in the "Update viable/strict" workflow.

[DanilBaibak]

Fixed the typo in the "Update viable/strict" workflow.

cc @seemethere

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/7441

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[pmeier]

LGTM, thanks @DanilBaibak! In other workflows that we don't typically run on a PR, we have this extra condition to run them in case the workflow is touched:

vision/.github/workflows/tests-schedule.yml

Lines 3 to 8 in f0a1df3

	on:
	pull_request:
	paths:
	- "test/test_datasets_download.py"
	- ".github/failed_schedule_issue_template.md"
	- ".github/workflows/tests-schedule.yml"

So here this would be

on:
  pull_request:
    paths:
      - ".github/workflows/update-viablestrict.yml"

In addition, we only perform the actual action like reporting an issue or fast-forwarding the branch in case this happens on a schedule:

vision/.github/workflows/tests-schedule.yml

Lines 47 to 49 in f0a1df3

	- uses: JasonEtco/create-an-issue@v2.4.0
	name: Create issue if download tests failed
	if: failure() && github.event_name == 'schedule'

With this setup you can avoid typo errors like this when working on the workflow, while not changing the actual functionality.

[DanilBaibak]

Yeah, let's add a trigger by modifying the workflow. Otherwise, it's hard to test the changes.

[pmeier]

Case in point: https://github.com/pytorch/vision/actions/runs/4488086872

[github-actions]

Hey @DanilBaibak!

You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py

[pmeier]

Workflow is green: https://github.com/pytorch/vision/actions/runs/4488123965/jobs/7892815057