Checklist

• I added a descriptive title
• I searched open reports and couldn't find a duplicate

What happened?

There are two conditions in which combine-durations may be triggered. The most common situation is via a scheduled run (see https://github.com/conda/conda/actions/runs/10232908263/job/28310609789) but with the new update.yml workflow the action may also be triggered manually (see https://github.com/conda/conda/actions/runs/10255189131/job/28371616702).

In either case if no PR exists then we end up cloning the upstream repo allowing combine-durations to correctly detect the repository to download artifacts from. However, if a PR already exists (which typically means the PR is made via a fork) then combine-durations will incorrectly detect the fork repo as the upstream and will attempt to download test artifacts from the fork (of which there will be none).

Conda Info

No response

Conda Config

No response

Conda list

No response

Additional Context

No response