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

Change results order to allow auto-merge #5788

Merged
merged 2 commits into from
Jun 19, 2024
Merged

Change results order to allow auto-merge #5788

merged 2 commits into from
Jun 19, 2024

Conversation

oseoin
Copy link
Contributor

@oseoin oseoin commented Jun 19, 2024

Proposed changes

Restructure CI final steps to allow auto-merge requirements without blocking docs-only workflows.

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING doc
  • I have added tests that prove my fix is effective or that my feature works
  • I have checked that all unit tests pass after adding my changes
  • I have updated necessary documentation
  • I have rebased my branch onto main
  • I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

@oseoin oseoin requested a review from a team as a code owner June 19, 2024 09:30
@github-actions github-actions bot added github_actions Pull requests that update Github_actions code chore Pull requests for routine tasks labels Jun 19, 2024
@oseoin oseoin merged commit e14716a into main Jun 19, 2024
80 checks passed
@oseoin oseoin deleted the auto-merge-fix branch June 19, 2024 10:10
ssrahul96 pushed a commit to ssrahul96/kubernetes-ingress that referenced this pull request Jun 20, 2024
change results order to allow auto-merge
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Pull requests for routine tasks github_actions Pull requests that update Github_actions code
Projects
Status: Done 🚀
Development

Successfully merging this pull request may close these issues.

4 participants