Cayleb-Ordo

@Stan` So i did retest it with the higher rights. [lfs] repositoryformatversion = 0 url = git@gitea.wildfiregames.com:0ad/0ad.git Thats the config, i did those commands: $ git lfs fetch 0ad-base main $ git lfs pull 0ad-base main $ git rebase -i 0ad-base/main $ git push ... To gitea.wildfiregames.com:Cayleb-Ordo/0ad.git 68a7abb3b3..6bdcab11b9 main -> main $ Seems to work.

No, pointing to my fork. Pushing did not work while configured to the main repository. I did try first without changing the config, to test if the gitea update changed something and after that i changed the setting and did the same commands again.

Oh nice i already tested it before u added me , the git lfs pull 0ad-base main worked without errors. (unix fashion no complaint is all right)

@Stan` Thx for the quick response. Tried it today again, now it works if i set the url to my fork. fetching and pulling from the 0ad-main repository is working.

Hello its me again. Having troubles again with the lfs... So fetching from the main repository works with the suggestion from the .lfsconfig. But i can no longer update my fork, its always trying to push directly to the main 0ad repository... Any ideas why? Same problem on windows and linux and on a clean checkout. Also did try the suggestion from this thread, but the effect was that it would never update again from the main 0ad repo. actual error: batch request: error:: 0% (0/1), 0 B | 0 B/s error: User: 1394:Cayleb-Ordo with Key: 34:Linux-PC is not authorized to write to 0ad/0ad. error:: exit status 1 local git config: core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true remote.origin.url=git@gitea.wildfiregames.com:Cayleb-Ordo/0ad.git remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* branch.main.remote=origin branch.main.merge=refs/heads/main branch.main.vscode-merge-base=origin/main remote.0ad-base.url=git@gitea.wildfiregames.com:0ad/0ad.git remote.0ad-base.fetch=+refs/heads/*:refs/remotes/0ad-base/* user.name=Cayleb-Ordo branch.build-with-cmake.remote=origin branch.build-with-cmake.merge=refs/heads/build-with-cmake branch.build-with-cmake.vscode-merge-base=origin/build-with-cmake lfs.repositoryformatversion=0 lfs.url=git@gitea.wildfiregames.com:0ad/0ad.git branch.build-with-cmake-initial.remote=origin branch.build-with-cmake-initial.merge=refs/heads/build-with-cmake-initial branch.build-with-cmake-initial.vscode-merge-base=origin/build-with-cmake lfs.https://gitea.wildfiregames.com/0ad/0ad.git.locksverify=false lfs.https://gitea.wildfiregames.com/Cayleb-Ordo/0ad.git.locksverify=true branch.build-with-cmake-backup.vscode-merge-base=origin/build-with-cmake remote configuration: 0ad-base git@gitea.wildfiregames.com:0ad/0ad.git (fetch) 0ad-base git@gitea.wildfiregames.com:0ad/0ad.git (push) origin git@gitea.wildfiregames.com:Cayleb-Ordo/0ad.git (fetch) origin git@gitea.wildfiregames.com:Cayleb-Ordo/0ad.git (push)

Thx that fixed it. Always forget that git lfs :D.

Hey guys, i updated a branch on my development fork. If i want to push the changes, ill have to enter my credentials even if i cloned it with my configured ssh key. Does anyone have the same problem ? And if i do that, than it will not accept it either. Had the problem bot on fedora 41 and opensuse tumbleweed.

Ok, then ill keep that. Only thing left now is to get the hang with Phabricator .

@Stan` regarding the docs Pipeline, is it necessary to build pyrogenesis? Or could that be removed and only build doxygen and the entity docs?

So, i tried to understand where to put the new Dockerfile. I located the build Pipeline for the Dockers, but the docs-Docker is not build there. My current understanding of the Pipelines is that in order to add a new Docker Image, i have to add it to the build-docker Pipeline and modify the Docs Pipeline. But i did not get where i can tell the Pipeline which image should be used. It would be great if i could be corrected if i am wrong. By the way, interesting way to use zfs pools. Never seen them used like this before.

Unterstood, then I will create a dockerfile only for the documentation. If i have time, i will test it with a self hosted jenkins server. Thought i give you the latest version of it.

@hyperion Do you know which is the right contact person to talk about changing this?

is there a way to test the ci stuff? I saw the docker files and they are on debian buster, which is old old stable.

I think it is more cross-platform and with the fetch_content we could get the doxygen-theme easily. Edit: Indeed, it is very simple to integrate the theme using cmake fetch_content.

I think the Todo List is automatically generated by Doxygen if something is marked with "@todo". It can be disabled in the doxygen config. I created a CMake File, that could also be used in a ci and locally. That limits the Version Numbering if used automatically to numbers. It could be set manually, if there is no "real" Version number. Ill try that. Another thing i dont realy know is, how the SVN can handle git submodules. The doxygen-awesome-css could be bundled like other libs already are, but i think the submodule option is the cleanest.