restrict how the azure-preview-env-deploy.yml workflow runs

[jsoref]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

This isn't specific to any particular article.

What changes are you suggesting?

This workflow: https://github.com/github/docs/blob/main/.github/workflows/azure-preview-env-deploy.yml (and quite possibly others) should be changed so that it checks to see if it has enough secrets to run in the repository in which it's running, and if not, quit gracefully.

(Alternatively, it could only run if the repository is github/docs or the internal repository...)

Additional information

There was a user who tried to make a pull request into their own fork of github/docs, and the results were not good

https://github.com/jaystyles/docs/runs/6728372344?check_suite_focus=true
https://github.com/jaystyles/docs/runs/6729214425?check_suite_focus=true
...
https://github.com/jaystyles/docs/runs/6753841425?check_suite_focus=true
...

https://github.com/jaystyles/docs/runs/6771319636?check_suite_focus=true
https://github.com/jaystyles/docs/runs/6771735158?check_suite_focus=true
https://github.com/jaystyles/docs/runs/6775149948?check_suite_focus=true
...

https://github.com/jaystyles/docs/runs/6787590305?check_suite_focus=true
...

[cmwilson21]

@jsoref Thanks so much for opening an issue! I'll triage this for the team to take a look 👀

[skedwards88]

I'm moving this from the content review board to the engineering review board.

[rachmari]

@jsoref thanks for reporting this. I've opened an internal issue with this bug report.

[rachmari]

@jsoref can you provide additional details about the failures you're seeing. A PR reference would help. The azure-preview-env-deploy.yml workflow does have sufficient secret access to deploy on forks of github/docs. If there are failures, there may be another reason.

[jsoref]

@rachmari: https://github.com/jsoref/github-docs/actions/runs/2794120405

[jsoref]

Grumble

[rachmari]

@jsoref sorry for not circling back around to this sooner. We took a look at this as a team and we think that this is part of an issue we're tracking where an intermittent issue with Azure creates a failed workflow run. This doesn't happen in a repeatable way but the workaround for this is to close the pull request and reopen it. The workflow does have the proper credentials needed to run the workflow in a fork of github/docs.

I'm sorry that you ran into this issue.