[Roland Knall <rknall@xxxxxxxxx>]

Hi everyone

For those of you using a forked repository, I just want to inform you of an issue some of you might be having but not being aware of. For the past few days it seems, Gitlab has issues updating a forked repository, thus affecting those of you who forked directly from Gitlab. As a result, you may not have a master branch in your forked repository, which uses the latest changes.

There already seems to be work done at gitlab in that area: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/7420 and others are tracking the issue.

For now, those affected have to revert to a manual update of their forked repository. You can do that by using the following two lines back to back in a CLI (that is assuming, you followed the naming scheme used in the documentation, with upstream being the main wireshark repository):

git pull upstream master:master

git push origin master

After that, your local and remote-forked branch should have the latest changes.

Btw, deleting your repo and forking again, will not resolve the issue.

cheers

Roland