Bastien Abadie

I'm looking into this and have a few questions: - there already exists [firefox source code checkouts](https://firefox-source-docs.mozilla.org/taskcluster/caches.html#version-control-caches) in Taskcluster cache, but they are restricted to tasks ran by run-task: would...

I noticed that we already have [cache enabled](https://github.com/mozilla/code-review/blob/master/integration/taskcluster-hook.json#L30) for the Integration hook. Unfortunately the [hook on Community TC](https://community-tc.services.mozilla.com/tasks/X-st65oCSg61OmEzwxGpIg/runs/0/logs/public/logs/live.log) does not successfully run anymore due to a missing secret. We could...

I spent a bit of time today on this topic and noticed a few things: - the integration test is broken because of invalid Taskcluster proxy url and automated conversion...

If the decision task is broken, we do not get the pulse message from `code-review-issues` ending task, so the bot is not triggered. The only way to do that is...

Inspired by https://github.com/La0/mozilla-sa-crasher

v1 will run in a community TC hook with a simple python 3 script that: 1. clone MC 2. apply a locally stored patch 3. publish it on phabricator-dev with...

v2 should have the following behaviours: - handle several patches on different repos (nss & mc) - use patch on rarely changed files (@abpostelnicu @marco-c any idea here ? )...

I looked into this issue and found that we get a `publishable=False` response from the backend for these warnings. As the backend only check if they are at error level...

> [@La0](https://github.com/La0) the warning mentioned in [#2665 (comment)](https://github.com/mozilla/code-review/issues/2665#issuecomment-3334296583) was not a full file one: Yes, I think it's a general issue (not only tied to full-file)

~~Any idea why some unit tests are not passing here ?~~ Just saw your previous comment afterward, so it may be unrelated to your changes