Try to display fully qualified branch names (i.e. user:branch) when regression-testing PRs that come from forked repositories. This should help avoid confusion (reported by @myreen and others) when a PR is made from a forked master branch, and it's unclear whether this is CakeML master or a forked master.
In particular:
Query the "repository owner" (i.e. username) when retrieving PRs from GitHub.
Record this owner in the "snapshot".
Prepend user: when converting the snapshot to a string if the owner is not CakeML.
This seems to suffice in local interactive tests: the on-disk saved snapshots contain the fully qualified name, which are then used to generate the HTML.
Try to display fully qualified branch names (i.e.
user:branch) when regression-testing PRs that come from forked repositories. This should help avoid confusion (reported by @myreen and others) when a PR is made from a forkedmasterbranch, and it's unclear whether this is CakeMLmasteror a forkedmaster.In particular:
user:when converting the snapshot to a string if the owner is not CakeML.This seems to suffice in local interactive tests: the on-disk saved snapshots contain the fully qualified name, which are then used to generate the HTML.