Andreas AhlenstorfandMathieu Fenniak
8a1021e2a0
A separate commit status is introduced for skipped checks. That enables marking them as such in the UI instead of successful, which could be misleading. Resolves https://codeberg.org/forgejo/forgejo/issues/10138. ## Checklist The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. All work and communication must conform to Forgejo's [AI Agreement](https://codeberg.org/forgejo/governance/src/branch/main/AIAgreement.md). There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org). ### Tests for Go changes (can be removed for JavaScript changes) - I added test coverage for Go changes... - [x] in their respective `*_test.go` for unit tests. - [x] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I ran... - [x] `make pr-go` before pushing ### Tests for JavaScript changes (can be removed for Go changes) - I added test coverage for JavaScript changes... - [ ] in `web_src/js/*.test.js` if it can be unit tested. - [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)). ### Documentation - [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. - [x] I did not document these changes and I do not expect someone else to do it. ### Release notes - [x] This change will be noticed by a Forgejo user or admin (feature, bug fix, performance, etc.). I suggest to include a release note for this change. - [ ] This change is not visible to a Forgejo user or admin (refactor, dependency upgrade, etc.). I think there is no need to add a release note for this change. *The decision if the pull request will be shown in the release notes is up to the mergers / release team.* The content of the `release-notes/<pull request number>.md` file will serve as the basis for the release notes. If the file does not exist, the title of the pull request will be used instead. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/12606 Reviewed-by: Cyborus <cyborus@disroot.org> Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>
108 lines
2.5 KiB
YAML
108 lines
2.5 KiB
YAML
-
|
|
id: 1
|
|
index: 1
|
|
repo_id: 1
|
|
state: "pending"
|
|
sha: "1234123412341234123412341234123412341234"
|
|
target_url: https://example.com/builds/
|
|
description: My awesome CI-service
|
|
context: ci/awesomeness
|
|
context_hash: c65f4d64a3b14a3eced0c9b36799e66e1bd5ced7
|
|
creator_id: 2
|
|
|
|
-
|
|
id: 2
|
|
index: 2
|
|
repo_id: 1
|
|
state: "warning"
|
|
sha: "1234123412341234123412341234123412341234"
|
|
target_url: https://example.com/coverage/
|
|
description: My awesome Coverage service
|
|
context: cov/awesomeness
|
|
context_hash: 3929ac7bccd3fa1bf9b38ddedb77973b1b9a8cfe
|
|
creator_id: 2
|
|
|
|
-
|
|
id: 3
|
|
index: 3
|
|
repo_id: 1
|
|
state: "success"
|
|
sha: "1234123412341234123412341234123412341234"
|
|
target_url: https://example.com/coverage/
|
|
description: My awesome Coverage service
|
|
context: cov/awesomeness
|
|
context_hash: 3929ac7bccd3fa1bf9b38ddedb77973b1b9a8cfe
|
|
creator_id: 2
|
|
|
|
-
|
|
id: 4
|
|
index: 4
|
|
repo_id: 1
|
|
state: "failure"
|
|
sha: "1234123412341234123412341234123412341234"
|
|
target_url: https://example.com/builds/
|
|
description: My awesome CI-service
|
|
context: ci/awesomeness
|
|
context_hash: c65f4d64a3b14a3eced0c9b36799e66e1bd5ced7
|
|
creator_id: 2
|
|
|
|
-
|
|
id: 5
|
|
index: 5
|
|
repo_id: 1
|
|
state: "error"
|
|
sha: "1234123412341234123412341234123412341234"
|
|
target_url: https://example.com/builds/
|
|
description: My awesome deploy service
|
|
context: deploy/awesomeness
|
|
context_hash: ae9547713a6665fc4261d0756904932085a41cf2
|
|
creator_id: 2
|
|
|
|
-
|
|
id: 6
|
|
index: 1
|
|
repo_id: 62
|
|
state: "failure"
|
|
sha: "774f93df12d14931ea93259ae93418da4482fcc1"
|
|
target_url: "/user2/test_workflows/actions"
|
|
description: My awesome deploy service
|
|
context: deploy/awesomeness
|
|
context_hash: ae9547713a6665fc4261d0756904932085a41cf2
|
|
creator_id: 2
|
|
|
|
-
|
|
id: 7
|
|
index: 6
|
|
repo_id: 1
|
|
state: "pending"
|
|
sha: "1234123412341234123412341234123412341234"
|
|
target_url: https://example.com/builds/
|
|
description: My awesome deploy service
|
|
context: deploy/awesomeness
|
|
context_hash: ae9547713a6665fc4261d0756904932085a41cf2
|
|
creator_id: 2
|
|
|
|
-
|
|
id: 8
|
|
index: 2
|
|
repo_id: 62
|
|
state: "error"
|
|
sha: "774f93df12d14931ea93259ae93418da4482fcc1"
|
|
target_url: "/user2/test_workflows/actions"
|
|
description: "My awesome deploy service - v2"
|
|
context: deploy/awesomeness
|
|
context_hash: ae9547713a6665fc4261d0756904932085a41cf2
|
|
creator_id: 2
|
|
|
|
-
|
|
id: 9
|
|
index: 7
|
|
repo_id: 1
|
|
state: "skipped"
|
|
sha: "1234123412341234123412341234123412341234"
|
|
target_url: https://example.com/builds/
|
|
description: Publish awesomeness
|
|
context: publish/awesomeness
|
|
context_hash: 701785a796917a4942f2ab1337d95225270026b5
|
|
creator_id: 2
|