PromucFlow_constructor/.github
Hetu Nandu b612a717f5
ci: Possible fix for Integration tests result update failures (#31600)
In testing we saw that updating `ci-test-result` has a chance of failing
if the correct check is not found.

When we are creating the `ci-test-result` check via the Github Api, it
successfully marked the PR check with the result. It did not seem to
have any issue even if a `ci-test-result` job already existed

By removing the logic of finding an existing check of the same name, and
always creating the check, we assume this will improve the PR check
updates

fixes: #31601
2024-03-08 11:17:00 +05:30
..
ISSUE_TEMPLATE Update --bug-report.yaml 2024-03-01 17:17:15 +05:30
workflows ci: Possible fix for Integration tests result update failures (#31600) 2024-03-08 11:17:00 +05:30
config-test.json chore: updated label config to let us add performance on any independent issue (#20009) 2023-01-25 15:21:22 +05:30
config.json Updated Label Config 2024-03-06 22:48:36 +05:30
config.yml chore: Update the welcome bot message (#16444) 2022-09-01 16:12:07 +05:30
labeler.yml ci: Using appsmith's fork of labeler for minor enhancement & easier config (#7177) 2021-09-06 22:48:35 +05:30
pull_request_template.md chore: Add JUnit option for the testcase type in PR template (#26560) 2023-08-22 15:15:44 +05:30
release-drafter-template.yml chore: increment minor number for snapshot versions (#30487) 2024-01-22 10:02:57 +05:30
reviewers.yml fix: Added DS pod as reviewer for all PR that changes client (#23635) 2023-05-23 15:04:16 +05:30
semantic.yml chore: Removing redundant toast message in action creation & deletion flow (#6998) 2021-09-01 03:40:44 +00:00