Fix pipeline incorrectly detecting 'trigger' as a branch name
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3571340. --> Reported by: [joevagyok](https://www.drupal.org/user/2876343) >>> <h3>Problem</h3> <p>The pipeline system was incorrectly treating 'trigger' port connections as branch names, causing issues with workflow execution and branch detection logic.</p> <h3>Root Cause</h3> <p>The branch name detection logic did not exclude the reserved 'trigger' port name from consideration.</p> <h3>Solution</h3> <p>Updated the branch detection logic to explicitly exclude 'trigger' from the list of potential branch names.</p> <h3>Impact</h3> <ul> <li>Correct branch detection for gateway nodes</li> <li>Trigger connections no longer interfere with branching logic</li> </ul>
issue