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

[8.10](backport #3587) Remove govulincheck from github actions #3596

Merged
merged 2 commits into from
Oct 12, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 12, 2023

This is an automatic backport of pull request #3587 done by Mergify.
Cherry-pick of e20c34d has failed:

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

You are currently cherry-picking commit e20c34d66d.
  (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)

Changes to be committed:
	modified:   .ci/bump-golang.yml

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

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


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

* remove govulincheck

* Revert "Enable running govulncheck in PRs (#3125)"

This reverts commit 1be6088.

(cherry picked from commit e20c34d)

# Conflicts:
#	.github/workflows/govulncheck.yml
@mergify mergify bot requested a review from a team as a code owner October 12, 2023 19:12
@mergify mergify bot added the backport label Oct 12, 2023
@mergify mergify bot removed the request for review from a team October 12, 2023 19:12
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Oct 12, 2023
@mergify mergify bot requested review from blakerouse and faec October 12, 2023 19:12
@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 12, 2023

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-10-12T20:41:39.434+0000

  • Duration: 27 min 47 sec

Test stats 🧪

Test Results
Failed 0
Passed 6317
Skipped 55
Total 6372

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages.

  • run integration tests : Run the Elastic Agent Integration tests.

  • run end-to-end tests : Generate the packages and run the E2E Tests.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 12, 2023

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 98.765% (80/81) 👍
Files 67.944% (195/287) 👍
Classes 66.234% (357/539) 👍
Methods 53.125% (1122/2112) 👍
Lines 38.638% (12770/33050) 👎 -0.018
Conditionals 100.0% (0/0) 💚

@fearful-symmetry fearful-symmetry merged commit 907a47f into 8.10 Oct 12, 2023
7 checks passed
@fearful-symmetry fearful-symmetry deleted the mergify/bp/8.10/pr-3587 branch October 12, 2023 23:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants