📝 Update docstring generator to include target branch for push

[Drewniok]

Description

The docstring generator workflow successfully runs when merging branches originating from upstream-main. However, it fails to push docstrings during workflow execution for branches originating from fork-main due to detached branches.

This PR resolves the issue by specifying the target branch for pushing docstrings.

Thanks @simon1hofmann for helping to figure this out!

Checklist:

• The pull request only contains commits that are related to it.
• I have added appropriate tests and documentation.
• I have added a changelog entry.
• I have created/adjusted the Python bindings for any new or updated functionality.
• I have made sure that all CI jobs on GitHub pass.
• The pull request introduces no new warnings and follows the project's style guidelines.

[simon1hofmann]

Then the changes of #475 can probably be reverted right?
on: push should be enough.

[simon1hofmann]

I think it's not possible to push to the branch like that, also add-and-commit should take care of that automatically.

[Drewniok]

ah great! Thank you!

[marcelwa]

@Drewniok @simon1hofmann does this work as intended now?

[Drewniok]

@marcelwa Not yet

[marcelwa]

Alright, keep me posted

[Drewniok]

@marcelwa It works now! Thanks @simon1hofmann for your help.

[marcelwa]

Why is this important?

[simon1hofmann]

Previously, the docstring generator only worked for branches forked directly from fiction and not, e.g., Drewniok/fiction, which lead to this error message:

Error: Error: fatal: You are not currently on a branch.
To push the history leading to the current (detached HEAD)
state now, use

  git push origin HEAD:<name-of-remote-branch>

By default, fetch-depth is set to 1, so something similar like this happens:
git fetch --depth 1 origin $GITHUB_REF

I guess this misses the forked branch.

[marcelwa]

Understood. Many thanks!