I actually don't think it'll need to speak arc/differential. In l18n-bot's case we want to skip review anyway, so we might just be able to let it push directly to the repo and skip making a differential.

Relevant code is at https://github.com/wikimedia/translatewiki/blob/ae74e2361a10f34c4996a225a34d3839e219f17a/bin/repocommit#L36 and https://github.com/wikimedia/translatewiki/blob/ae74e2361a10f34c4996a225a34d3839e219f17a/bin/repocommit#L138.

In T92493#1112872, @demon wrote:

I actually don't think it'll need to speak arc/differential. In l18n-bot's case we want to skip review anyway, so we might just be able to let it push directly to the repo and skip making a differential.

I agree with this. With the new differential you cannot review your own patchset (by default, which I think it's regression) and it's useless to review bunch of patches created by bot that we know what it does.

In T92493#1112872, @demon wrote:

I actually don't think it'll need to speak arc/differential. In l18n-bot's case we want to skip review anyway, so we might just be able to let it push directly to the repo and skip making a differential.

Long-term we do want l10n-bot to go through CI for things like T91707: L10n-bot should not force-merge / override Jenkins (breaks the build).

In T92493#1780874, @Legoktm wrote:

In T92493#1112872, @demon wrote:

I actually don't think it'll need to speak arc/differential. In l18n-bot's case we want to skip review anyway, so we might just be able to let it push directly to the repo and skip making a differential.

Long-term we do want l10n-bot to go through CI for things like T91707: L10n-bot should not force-merge / override Jenkins (breaks the build).

Long term I'd love a world where we don't have to make gigantic daily commits to 100+ repos just to update l10n.

In T92493#1780878, @demon wrote:

Long term I'd love a world where we don't have to make gigantic daily commits to 100+ repos just to update l10n.

They are not very gigantic imho, just numerous. Plans for "LUServer" do exist, it was also proposed for GSoC project.

@demon said we can use plain git (push?) which we already support. I don't know how that will go with the projects which want to run tests for l10n changes.

Will also need the l10n-bot account / permissions sorted out.

And finally, gerrit provides a list of repositories. Does Phabricator have equivalent? In a way that we can easily grep extensions and skins?

In T92493#1915300, @Nikerabbit wrote:

@demon said we can use plain git (push?) which we already support. I don't know how that will go with the projects which want to run tests for l10n changes.

We could have it go async. The changes could be tested by Jenkins after pushing and report back via Audit if a problem is encountered.

Will also need the l10n-bot account / permissions sorted out.

Not hard, just needs to be setup especially in a way that's pretty automated going forward so we don't have to manually set things up all the time.

And finally, gerrit provides a list of repositories. Does Phabricator have equivalent? In a way that we can easily grep extensions and skins?

Yes. There's conduit's repository.query but it's currently "unstable" and might need a little more work to get the exact data out we want.

Just spoke with James about this in the office this morning. Siebrand did work to make l10n bot to work with github at the hackathon so presumably it is now much easier to add additional git push locations in l10n bot.

A good test case could be OOUI? They want to be an early adopter of Differential as well (T122834).

Any repo should do. I just need to know whether Differential uses git push or something else.

Example of the new repong configs you referred to: https://gerrit.wikimedia.org/r/#/c/281308

In T92493#2195518, @Nikerabbit wrote:

Any repo should do. I just need to know whether Differential uses git push or something else.

Since we don't need code-review of (all of) these commits a simple git push of the commit works (assuming the user pushing has the needed rights).

For repos that the owners want to actually review the changes you could use arc diff or wait for us to solve the "don't require arc" issue (T127).

In T92493#2195766, @greg wrote:

In T92493#2195518, @Nikerabbit wrote:

Any repo should do. I just need to know whether Differential uses git push or something else.

Since we don't need code-review of (all of) these commits a simple git push of the commit works (assuming the user pushing has the needed rights).

For repos that the owners want to actually review the changes you could use arc diff or wait for us to solve the "don't require arc" issue (T127).

Ideally, all those patches would be merged automatically when tests pass. So far we have gone the other way because testing infrastructure is not able to take the load (maybe changed now?) and tests are more often failing for unrelated reasons rather than us breaking something (this should change though).

But we can certainly do git push right now. We are not yet prepared for mass migration of MediaWiki extensions, but other projects should be fine.