Alexander Bayandin 3e8bf2159d CI(build-and-test): run benchmarks after deploy job (#10791) ...

## Problem

`benchmarks` is a long-running and non-blocking job. If, on Staging, a
deploy-blocking job fails, restarting it requires cancelling any running
`benchmarks` jobs, which is a waste of CI resources and requires a
couple of extra clicks for a human to do.

Ref: https://neondb.slack.com/archives/C059ZC138NR/p1739292995400899

## Summary of changes
- Run `benchmarks` after `deploy` job
- Handle `benchmarks` run in PRs with `run-benchmarks` label but without
`deploy` job.

2025-02-13 22:03:47 +00:00

..

actions

Enable sanitizers for postgres v17 (#10401)

2025-02-06 12:53:43 +00:00

ISSUE_TEMPLATE

[infra/notes] impr: add issue types to issue templates (#10018)

2025-01-31 06:29:06 +00:00

PULL_REQUEST_TEMPLATE

Migrate links from wiki to notion (#5862)

2023-11-14 15:36:47 +00:00

workflows

CI(build-and-test): run benchmarks after deploy job (#10791)

2025-02-13 22:03:47 +00:00

actionlint.yml

Move cargo-deny into a separate workflow on a schedule (#10289)

2025-01-31 13:42:59 +00:00

file-filters.yaml

Move cargo-deny into a separate workflow on a schedule (#10289)

2025-01-31 13:42:59 +00:00

pull_request_template.md

Remove checklist from the PR template (#9702)

2024-11-11 17:01:02 +00:00