Skip to content

Commit a91814b

Browse files
committed
fixing typo
1 parent ee4c926 commit a91814b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_posts/2022-10-12-using-github-checks-api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: 'Using the GitHub Checks API to Link Workflow Statuses in a PR'
33
author: Josh Johanning
44
date: 2022-10-12 20:30:00 -0500
5-
description: Using the GitHub Checks API to report back the status of another GitHub Action workflow triggered via the workflow_dispatch event in a pull request
5+
description: Using the GitHub Checks API to report the status of another workflow back to the pull request for gating purposes
66
categories: [GitHub, Actions]
77
tags: [GitHub, Scripts, gh cli]
88
mermaid: true
@@ -27,7 +27,7 @@ To summarize, this is the flow and challenge statement:
2727
5. The label update workflow calls the [deployment workflow](https://github.com/colindembovsky/mindaro/blob/main/.github/workflows/deploy-component.yml#L5) via the `workflow_dispatch` event
2828
6. The label job shows up as a status check in the PR
2929
7. The deployment job runs
30-
8. We want to post back to the PR the status of the deployment jo, but because the job wasn't created by the PR, it doesn't show up as a status check on the PR
30+
8. We want to post back to the PR the status of the deployment job, but because the job wasn't created by the PR, it doesn't show up as a status check on the PR
3131

3232
The status checks are shown on the image below. Notice how the job to label the PR shows up here, but not the job the subsequent job queued programmatically via the `workflow_dispatch` event:
3333

0 commit comments

Comments
 (0)