In this deployment window: https://wikitech.wikimedia.org/wiki/Deployments#deploycal-item-20251030T2000, the backports for this task T406170: Metric anomaly in resourceloader_build_seconds after 26 June 2025 were deployed, but if you check the comments section on that task, you won't see any deployment activity. What happened?

I learned that sometimes, when a deployment window is full/has a lot of patches, especially when they're not strictly config patches (fast to deploy), actual patches on train branches, sometimes deployers would +2 patches ahead of the window to save time. I did this and gave up my slot to another deployer to start with their config patch.

While they were in the middle of deploying their config patch, Scap auto-detected changes to the wmf.25 branch, and I asked the deployer to sync their changes together with mine. But since Scap uses Gerrit change ID to log activities on the associated task (as I understand), it syncs the changes but doesn't notify on the task linked above.

Notice that the task linked above doesn't include any activity (logs) for backport deployment, even though all the patches were deployed (the activity was silent).

small feature request

Is it possible for scap to log deployment activity on changes (if they have an associated task) that it autodetects during another deployment (of course, if the deployer accepts to deploy them)? So that the activity and deployment are visible to the tasks associated with the changes that were autodetected on a train branch?

I'm not sure if it's a good or bad idea, but I would let RelEng experts decide if it's useful.