|
Repo Added
|
Build
241
Last
|
Files
8
|
Badge
README BADGES
|
push
github
Docs: document gerrit workflow filename matching and naming The "GitHub Workflow Configuration" section stated only that a triggered workflow filename "must contain 'gerrit'" and "must contain the search filter". That is accurate but under-specified, and operators have been surprised by three behaviours that follow directly from the matching implementation in ``github.filter_workflows`` / ``filter_path``: * The test is ``path.lower().find(filter) >= 0`` -- a case-insensitive *substring* match anywhere in the filename, not a prefix or exact match. * gerrit-to-platform dispatches *every* workflow that matches an event, not just one. Any file whose name contains ``gerrit`` and the event filter fires; e.g. both ``gerrit-maven-merge.yaml`` and ``gerrit-release-merge.yaml`` run on every change-merged event. * For comment-added, the search filter is the value mapped to the keyword in ``[mapping "comment-added"]``, so the workflow filename must contain that mapped filter (not the keyword itself). Document the recommended ``gerrit-<description>-<event>.yaml`` naming convention, spell out the substring / all-matching-workflows-fire semantics, add the resulting cautions (avoid unintended name collisions; workflows that must not act on every event have to self-gate), and give a worked comment-added example (``stage-release = stage`` -> ``gerrit-maven-stage.yaml``). Documentation-only change; no code or behaviour is affected. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Change-Id: Iaa6e05c67 Signed-off-by: Anil Belur <abelur@linuxfoundation.org>
522 of 560 relevant lines covered (93.21%)
0.93 hits per line
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|
![]() |
Badge your Repo: releng-gerrit_to_platformWe detected this repo isn’t badged! Grab the embed code to the right, add it to your repo to show off your code coverage, and when the badge is live hit the refresh button to remove this message.Could not find badge in README. |
|
Embed ▾
README BADGES
|