[openssl/openssl] 137bcf: ci: name the second reader of the dispatch run-name

  Branch: refs/heads/master
  Home:   https://github.com/openssl/openssl
  Commit: 137bcf0a170e16a6c934f83b7e67082ab04bd400
      https://github.com/openssl/openssl/commit/137bcf0a170e16a6c934f83b7e67082ab04bd400
  Author: Georgy Karataev <[email protected]>
  Date:   2026-08-08 (Sat, 08 Aug 2026)

  Changed paths:
    M .github/workflows/ct-validation-daily.yml
    M .github/workflows/run-checker-daily.yml
    M .github/workflows/valgrind-daily.yml

  Log Message:
  -----------
  ci: name the second reader of the dispatch run-name

The run-name of a dispatched workflow is parsed by two services, not one: the CI
bot correlates a run with its check-run, and the Actions statistics collector
attributes CI load to the pull request that caused it. Neither validates the
string, so a mis-copied run-name is silent in both. The comment named only the
first reader, which understates what editing that line costs.

Assisted-by: Claude Opus 5 (1M context) <[email protected]>

Reviewed-by: Dmitry Misharov <[email protected]>
Reviewed-by: Milan Broz <[email protected]>
Reviewed-by: Norbert Pocs <[email protected]>
Reviewed-by: Andrew Dinh <[email protected]>
MergeDate: Sat Aug  8 15:34:01 2026
(Merged from https://github.com/openssl/openssl/pull/32174)


  Commit: eb5626c572691d50ad7a580e1a66291400114af6
      https://github.com/openssl/openssl/commit/eb5626c572691d50ad7a580e1a66291400114af6
  Author: Georgy Karataev <[email protected]>
  Date:   2026-08-08 (Sat, 08 Aug 2026)

  Changed paths:
    M .github/workflows/avx512-sde.yml
    M .github/workflows/compiler-zoo.yml
    M .github/workflows/run-checker-merge.yml

  Log Message:
  -----------
  ci: let the CI bot dispatch the compiler, merge and AVX512 zoos

These three only run after the fact: compiler-zoo and run-checker-merge on a
push, avx512-sde on a nightly cron. Their coverage therefore lands once a pull
request is already merged, which is when it is most expensive to act on.

Give all three the dispatch entry point the daily workflows already have:
validated pr/head_sha/check_run_id inputs, the run-name both services correlate
on, concurrency keyed on the pull request, and every checkout pinned to the
requested commit.

Existing behaviour is untouched. A push or a cron carries no inputs, so the
validator is skipped and each checkout falls back to github.sha -- the build jobs
still run on a push to a fork branch, the only pre-merge signal a contributor
gets here. The jitter library stays pinned to its release tag: a dispatched run
may choose the OpenSSL tree, never its dependencies.

Refs: openssl/project#2027

Assisted-by: Claude Opus 5 (1M context) <[email protected]>

Reviewed-by: Dmitry Misharov <[email protected]>
Reviewed-by: Milan Broz <[email protected]>
Reviewed-by: Norbert Pocs <[email protected]>
Reviewed-by: Andrew Dinh <[email protected]>
MergeDate: Sat Aug  8 15:34:06 2026
(Merged from https://github.com/openssl/openssl/pull/32174)


Compare: https://github.com/openssl/openssl/compare/1261c82f1e8a...eb5626c57269

To unsubscribe from these emails, change your notification settings at https://github.com/openssl/openssl/settings/notifications

-- 
You received this message because you are subscribed to the Google Groups "openssl-commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-commits/openssl/openssl/push/refs/heads/master/1261c8-eb5626%40github.com.