Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

github-action: delete opentelemetry workflow (backport #39559) #39683

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 23, 2024

Details

⚠️ This PR was created by an automated tool. Please review the changes carefully. ⚠️

We want to delete the opentelemetry workflow.

Why

We now support Observing the CICD at large scale without the need to use a specialised
workflow.

Further details

https://ela.st/oblt-ci-cd-stats is the place to see the traces and logs for
all the GitHub actions.

There will be one service per GitHub repository, including the org name, and
one Transaction per Workflow.

If there are any questions, please reach out to the @elastic/observablt-ci


This is an automatic backport of pull request #39559 done by [Mergify](https://mergify.com).

(cherry picked from commit 8b58916)

# Conflicts:
#	.github/workflows/opentelemetry.yml
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label May 23, 2024
Copy link
Contributor Author

mergify bot commented May 23, 2024

Cherry-pick of 8b58916 has failed:

On branch mergify/bp/7.17/pr-39559
Your branch is up to date with 'origin/7.17'.

You are currently cherry-picking commit 8b58916153.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: .github/workflows/opentelemetry.yml

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 23, 2024
@botelastic
Copy link

botelastic bot commented May 23, 2024

This pull request doesn't have a Team:<team> label.

@v1v v1v closed this May 23, 2024
@mergify mergify bot deleted the mergify/bp/7.17/pr-39559 branch May 23, 2024 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conflicts There is a conflict in the backported pull request needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant