Fix #14687 (Move repository from danmar to cppcheck-opensource)

[danmar]

No description provided.

[firewave]

Err - how do you move forks if the upstream repo moves?

Please update the daca client version.

And I assume this will wreck havoc on daca for quite a while since all clients need to be updated otherwise they will pull outdated code. And we need to make sure the transition within daca just works if the repo changes.

Any other surprises like this happening soon?

[firewave]

And there's also the external integrations in OSS-Fuzz, Codecov and Coverity which need to be checked.

[danmar]

Err - how do you move forks if the upstream repo moves?

personally I used these commands:

git remote remove upstream
git remote add upstream git@github.com:cppchek-opensource/cppcheck.git

And there's also the external integrations in OSS-Fuzz, Codecov and Coverity which need to be checked.

I have updated Codecov and Coverity integrations as far as I know.

[danmar]

Any other surprises like this happening soon?

No.

[chrchr-github]

Err - how do you move forks if the upstream repo moves?

There seems to be some kind of redirect, I didn't have to make any changes locally.

Please update the daca client version.

And I assume this will wreck havoc on daca for quite a while since all clients need to be updated otherwise they will pull outdated code. And we need to make sure the transition within daca just works if the repo changes.

daca has been mostly down anyway in recent weeks, so we would hardly notice.

[danmar]

oss-fuzz PR: google/oss-fuzz#15410

[danmar]

There seems to be some kind of redirect, I didn't have to make any changes locally.

+1 thanks!
Do you see if the syncing from upstream works fine?

as far as I know, I only use my remote "upstream" when I want to access release branches.

[chrchr-github]

There seems to be some kind of redirect, I didn't have to make any changes locally.

+1 thanks! Do you see if the syncing from upstream works fine?

Pulls work, haven't tried much else yet.

[firewave]

I would prefer not to do a major version jump in daca if it still works (will test later). That should be reserved for when we really change the API. Also it seems weird that the 2.x client would work with the 1.x server.