Discussion: Tag triggers vs release triggers in CI templates

[CybotTM]

The CI templates trigger on tag push rather than release creation:

GitHub Actions:

on:
  push:
    tags:
      - '*'

GitLab CI:

rules:
  - if: $CI_COMMIT_TAG

(Note: only: tags is deprecated, rules is now recommended)

Context

GitHub Actions supports triggering on release events:

on:
  release:
    types: [published]

However, GitLab CI has no equivalent - releases are treated as pipeline outputs, not triggers. There's an open feature request for this capability.

Question

Is the current tag-based approach intentionally chosen for cross-platform consistency?

For GitHub-only users, release triggers offer benefits:

• More deliberate action (tag push can be accidental)
• Draft release notes can be reviewed before TER publish

But maintaining two different trigger strategies would add complexity.

Just curious if this was a deliberate architectural decision or if there's interest in documenting the trade-offs.