[chore] use opentelemetrybot

[codeboten]

This works around the limitation that a PR created by an action doesn't trigger workflows automatically by using the opentelemetrybot's token. See https://github.com/open-telemetry/community/blob/main/assets.md#opentelemetry-bot

Signed-off-by: Alex Boten [email protected]

[runforesight]

Foresight Summary

    
Major Impacts
Foresight hasn't detected any major impact on your workflows and tests.

View More Details

⭕  build-and-test-windows workflow has finished in 6 seconds (40 minutes 31 seconds less than main branch avg.) and finished at 24th Jan, 2023.

---

Job	Failed Steps	Tests
windows-unittest-matrix	-     🔗	N/A	See Details
windows-unittest	-     🔗	N/A	See Details

---

⭕  changelog workflow has finished in 5 seconds (1 minute 59 seconds less than main branch avg.) and finished at 24th Jan, 2023.

---

Job	Failed Steps	Tests
changelog	-     🔗	N/A	See Details

---

✅  telemetrygen workflow has finished in 9 minutes 31 seconds (⚠️ 7 minutes 4 seconds more than main branch avg.) and finished at 24th Jan, 2023.

---

Job	Failed Steps	Tests
build-dev	-     🔗	N/A	See Details
publish-latest	-     🔗	N/A	See Details
publish-stable	-     🔗	N/A	See Details

---

✅  prometheus-compliance-tests workflow has finished in 10 minutes 46 seconds (⚠️ 3 minutes 14 seconds more than main branch avg.) and finished at 24th Jan, 2023.

---

Job	Failed Steps	Tests
prometheus-compliance-tests	-     🔗	✅ 21  ❌ 0  ⏭ 0    🔗	See Details

---

✅  check-links workflow has finished in 8 minutes 49 seconds (⚠️ 6 minutes 58 seconds more than main branch avg.) and finished at 24th Jan, 2023.

---

Job	Failed Steps	Tests
changed files	-     🔗	N/A	See Details
check-links	-     🔗	N/A	See Details

---

✅  tracegen workflow has finished in 9 minutes 50 seconds (⚠️ 7 minutes 23 seconds more than main branch avg.) and finished at 24th Jan, 2023.

---

Job	Failed Steps	Tests
build-dev	-     🔗	N/A	See Details
publish-latest	-     🔗	N/A	See Details
publish-stable	-     🔗	N/A	See Details

---

✅  load-tests workflow has finished in 15 minutes 58 seconds and finished at 24th Jan, 2023.

---

Job	Failed Steps	Tests
loadtest (TestIdleMode)	-     🔗	✅ 1  ❌ 0  ⏭ 0    🔗	See Details
loadtest (TestTraceAttributesProcessor)	-     🔗	✅ 3  ❌ 0  ⏭ 0    🔗	See Details
loadtest (TestMetric10kDPS|TestMetricsFromFile)	-     🔗	✅ 6  ❌ 0  ⏭ 0    🔗	See Details
loadtest (TestMetricResourceProcessor|TestTrace10kSPS)	-     🔗	✅ 12  ❌ 0  ⏭ 0    🔗	See Details
loadtest (TestTraceNoBackend10kSPS|TestTrace1kSPSWithAttrs)	-     🔗	✅ 8  ❌ 0  ⏭ 0    🔗	See Details
loadtest (TestBallastMemory|TestLog10kDPS)	-     🔗	✅ 19  ❌ 0  ⏭ 0    🔗	See Details
setup-environment	-     🔗	N/A	See Details
loadtest (TestTraceBallast1kSPSWithAttrs|TestTraceBallast1kSPSAddAttrs)	-     🔗	✅ 10  ❌ 0  ⏭ 0    🔗	See Details

---

 build-and-test workflow has finished in 25 minutes 52 seconds (25 minutes 57 seconds less than main branch avg.) and finished at 24th Jan, 2023.

---

Job	Failed Steps	Tests
unittest-matrix (1.18, internal)	N/A	✅ 561  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, internal)	N/A	✅ 561  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, extension)	N/A	✅ 528  ❌ 0  ⏭ 0    🔗	See Details
correctness-metrics	N/A	✅ 2  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, processor)	N/A	✅ 1470  ❌ 0  ⏭ 0    🔗	See Details
correctness-traces	N/A	✅ 17  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, extension)	N/A	✅ 528  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, processor)	N/A	✅ 1470  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, receiver-0)	N/A	✅ 2567  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, exporter)	N/A	✅ 2429  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, receiver-1)	N/A	✅ 1895  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, other)	N/A	✅ 4629  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, receiver-1)	N/A	✅ 1895  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, other)	N/A	✅ 4629  ❌ 0  ⏭ 0    🔗	See Details
integration-tests	N/A	✅ 55  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, exporter)	N/A	✅ 2429  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, receiver-0)	N/A	✅ 2567  ❌ 0  ⏭ 0    🔗	See Details

---

🔎 See details on Foresight

^{*You can configure Foresight comments in your organization settings page.}

[TylerHelmuth]

@codeboten from the bot's description, do we need to do this?

Maintainers can open an issue in the community repository to have their repository granted access to this organization secret.

[codeboten]

@TylerHelmuth I'll test the workflow, after talking to trask, he indicated that public repos in the org may already have access to it.