We currently hard-code the schedulerId to `taskcluster-github`, and that means there's a lot of cross-talk between the staging and production instances.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.