I’m having issues where my actions are firing on the correct branches (based on the filters/triggers in their
yaml files) but are showing the incorrect branch as the source
This gave me concern initially when my feature/bug branches were firing off staging deploys, and my develop/master branches were running quality checks meant for feature/bug branches.
When I dug into it, it seems to be tied to merges. If I merge develop into a feature branch and make a push to the feature branch, actions will report the branch that activated the action as “develop”. And if I merge a feature branch into develop, the action will report being triggered by “feature/name-goes-here”.
It might be a small edge case, but it effects filtering as well. Is this a known issue, or should I be doing something to work around this?
You can see it below, the first commit was done directly into develop, and the second triggered when I merged that commit into my feature branch and pushed it
CI-Quality only runs on feature branches, and deploy staging only runs on develop, but both report being generated by develop