Michael Förderer

> Copied the changed reference files for all tests from a succesful run in Ubuntu 18.04 vm Shall I update the reference for you?

The function signature is: ```python def fork_repository_new_project(self, project_key, repository_slug, new_project_key, new_repository_slug): ``` You should change the order of the last two arguments.

If I get the docs right you can use this as pattern. I'm missing the enumeration of selector values in the docs. https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/pipelines/#post

Can you try to set `params=data` instead of `data=data`? This should add the parameters instead of a JSON payload.

> So I wonder when can the formal solution be released? The formal solution is to define a function with the same name always at the same line. For now...

@mawillers Following definition should fix your problem: ```c static constexpr bool isSafe = #if defined(USE_SAFE_FALLBACK) true; #else false; #endif

Ok, that was a misunderstanding from my side. Can you check the function names generated in the gcov files (option `--keep`)? In the case of the error they should be...

@mawillers I can reproduce it but I have no idea how to workaround this internal in gcovr. The functions are realy defined at different lines. If #663 is merged w...

You should be able to merge the Jason with an appended base directory and run the HTML generation withe the merged file.

The following function should support this (argument `kind`). https://github.com/atlassian-api/atlassian-python-api/blob/e8142c60ddbb1678e4b031a3abb64375cfe4df67/atlassian/bitbucket/cloud/repositories/branchRestrictions.py#L13