brandonchinn178 / brandonchinn178/mergit

Support specifying github actions in mergit.yml

Open
#227 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Haskell
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

GitHub actions are represented in the GitHub API separately from the Commit statuses API. So we should support both.

```yml
# .mergit.yaml
expected:
statuses:
- ci/circleci: asdf
workflows:
"My workflow":
- build
- test
```
(transition: top-level `statuses` alias for `expected: { statuses: ... }`)

Graphql query:
```gql
query {
repository(...) {
object(...) {
... on Commit {
status {
# "ci/circleci: asdf"
contexts { context }
}
checkSuites(...) {
nodes {
workflowRun {
# "My workflow"
workflow { name }
}
checkRuns(...) {
# "build" + status
nodes { name, status }
}
}
}
}
}
}
}
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the .mergit.yaml example and the GraphQL query in the issue, then trace how expected statuses are read and checked against GitHub commit data. Support workflows alongside statuses, including workflow names and check-run names, while preserving the top-level statuses alias; done means both representations are evaluated correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, graphql, haskell
Domain
backend-api-design, ci-cd
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.