Problem

The pipeline system was incorrectly treating 'trigger' port connections as branch names, causing issues with workflow execution and branch detection logic.

Root Cause

The branch name detection logic did not exclude the reserved 'trigger' port name from consideration.

Solution

Updated the branch detection logic to explicitly exclude 'trigger' from the list of potential branch names.

Impact

  • Correct branch detection for gateway nodes
  • Trigger connections no longer interfere with branching logic

Comments

joevagyok created an issue. See original summary.

gxleano’s picture

gxleano commented

I have contributed (not only by code, but discussion, presentation, testing or anything related).

d34dman’s picture

d34dman commented
Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.