Trask Stalnaker
Trask Stalnaker
I've renamed the old renovate onboarding PR: [open-telemetry/opentelemetry-collector-releases#426](https://github.com/open-telemetry/opentelemetry-collector-releases/pull/426) and deleted that PR's branch: [`renovate/configure`](https://github.com/open-telemetry/opentelemetry-collector-releases/tree/renovate/configure) based on https://github.com/renovatebot/renovate/blob/main/docs/usage/getting-started/installing-onboarding.md#nuke-config-and-re-onboard, it sounded like it could take a few hours for Renovate to notice...
@mowies let us know if everything is good, and if it's ok to close this issue, thanks!
sure, we can keep this issue open until you're able to confirm everything is working correctly IIRC, you disable dependabot by removing the `.github/dependabot.yml` file from the repo. Try that...
> Migrate all existing usages of [`runs-on: self-hosted`](https://github.com/search?q=org%3Aopen-telemetry+%22runs-on%3A+self-hosted%22+language%3AYAML&type=code) to `runs-on: equinix-bare-metal` PRs have been sent to all the repos that are using `runs-on: self-hosted`.
@open-telemetry/python-maintainers @open-telemetry/javascript-maintainers can you review the two PRs below? we need all existing repos to migrate to the new label before we can move forward with adding a second `self-hosted`...
@scottgerring @cijothomas the new self-hosted runner is available now you can see an example here: https://github.com/open-telemetry/sig-project-infra/pull/43/files @scottgerring using a container-based workflow will give you the chance to pick a container...
btw, I've given access to opentelemetry-rust and otel-arrow repos, with no restrictions on workflows / git refs for now so you can test it out via PRs like in the...
it helps with mitigation, but doesn't help with the initial confusion where the reviewers listed on PRs is empty for external contributors I sort of like this proposal > Assuming...
(didn't mean to close)
@zeitlinger was your recent work in #11620, #11667, and #12083 with the goal of working towards stabilizing the http instrumentation?