development branch build behaves as intended?

[Raphael-Gazzotti]

The development branch is currently being triggered by the creation of new branches for pull requests when using the option "Create a new branch for this commit and start a pull request". As a result, when a PR is created in this way, the development branch is built based on the modifications made by the new branch.
This does not appear to be the intended behavior.

Reference examples:

• Development branch of openMINDS commit a885778e8561e9f61fd343e25653eb9cfd29a06a
• Related branch and PR in openMINDS_chemicals:

1. Branch
2. PR#18

[Raphael-Gazzotti]

Looking closer at it, the PR did trigger the pipeline, but the changes aren’t based on this branch.

The function here:

openMINDS/openMINDS_pipeline/utils.py

Line 123 in 93438c4

def _evaluate_branch_and_commit_for_dynamic_instances(module_spec:OpenMINDSModule):

prevents that, both when a branch is set directly and when it’s chosen via regex.

However, what’s odd is that these changes weren’t already in dev from a previous submodule merge.