Deprecate `update-release-status.yml` workflow
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, github-actions, javascript
Research direction
Compare the update-release-status.yml workflow with scripts/release/webhook-handler.js to identify the release-state logic that should move into the Azure Function. Confirm that the function can dispatch update-status.yml after all check-runs conclude, then deprecate the workflow once the equivalent behavior is represented there.
Written by the indexing model from the issue text.
Description
The update-release-status.yml workflow is responsible to monitor the overall states of a release and dispatch the update-status.yml if all the check-runs successfully concluded.
The initial goal was to respond to check run events, but GitHub Actions doesn't dispatch this event generated by workflows to prevent divergent execution.
To reintroduce this behavior we have implemented an Azure Function that dispatches the update-release-status.yml workflow.
This Azure Function implemented in webhook-handler.js can include all the logic in update-release-status.yml.
- Dominant language
- CodeQL
- Stars
- 227
- Forks
- 82
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/codeql-coding-standards
-
false positive/false negative Stardard-MISRA-C++
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/codeql-coding-standards#1172 ·
-
Difficulty-Low false positive/false negative false-negative Impact-Low Standard-MISRA-C
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty-Medium false positive/false negative false-positive Impact-Medium Standard-CERT-C
Difficulty 4/5 3-5 days Newbie friendliness 48/100
github/codeql-coding-standards#1200 ·
-
`RULE-0-0-1`: "unreachable statement" false positives due to over-pruning of the control-flow graph Openfalse positive/false negative
Difficulty 4/5 3-5 days Newbie friendliness 48/100
github/codeql-coding-standards#1190 ·
-
false positive/false negative
Difficulty 3/5 1-2 days Newbie friendliness 65/100
github/codeql-coding-standards#1175 ·
All issues in github/codeql-coding-standards
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
vicharanashala/fln#564 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
haskell-actions/setup#152 ·
-
feature-request helm
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gravitational/teleport#69785 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
TencentCloud/Octop#1007 ·