I believe there is an API to create a local copy, but I'm not sure
I don't think Git has built-in support for that, but there seems to be some syntax/language aware diff tools that can be configured as the difftool.
I also use Azure Devops + GitHub - What kind of integration are you looking for?
Not really "looking for" it but what I meant was "pushing to GitHub packages from Azure Pipelines."
If you’re using Azure as the build server, you can also publish your Nugets into a private feed in Azure
That's what we do at the moment for private feeds.
If you are not using Azure Devops, GitHub Packages (as suggested by @nibblebit@programming.dev) can be worth looking into. They have a generous free tier.
No, since you are an admin I thought you might have a different view of things when you legged in.
Yes, I see them there. Is it possible that a higher level comment you are replying to has been deleted?
I don't see your comments. But I cannot see snowe's comments that you replied to, either. I suspect those comments are dangling for some reason.
Edit: I cannot tell the comment structure, but could it be such that a high/top level comment you are responding is deleted?
Interactive rebase is used to organize (squash, drop, reorder) commits and with some experience is totally painless. Would definitely recommend watching a few videos about it.
There is Git Large File Storage for that. But there may of course be alternatives that are better suited for that kind of tasks.
Now that you know the problem, do you think there would have been a way where git bisect would have found the problem? I don't know how your dependencies are handled, but if they are part of the code base (like NuGet packages referenced from project files) then I would expect bisect to find the offending commit where the dependency is bumped?

Thanks for the response. It sucks to not have language being set in some implementations of ActivityPub. I think separating the write language settings from the read language settings would help a bit to set the corrent language when writing, at least. But I suspect that needs to be fixed in the core Lemmy (not instance specific).