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.

Sign up for GitHub

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

Jump to bottom

Enforce the requirement for Pull Requests to pass both unit tests and integration tests before being added to the Merge Queue. #4334

Closed
eval-exec opened this issue Jan 30, 2024 · 2 comments
Closed

Enforce the requirement for Pull Requests to pass both unit tests and integration tests before being added to the Merge Queue. #4334

eval-exec opened this issue Jan 30, 2024 · 2 comments
Labels
stale To be closed due to a lack of activity t:ci Type: CI t:enhancement Type: Feature, refactoring.

Comments

@eval-exec
Copy link
Collaborator

Feature Request

Is your feature request related to a problem? Please describe.

Currently, the CI process allows pull requests to be added to the merge queue regardless of whether they have passed the necessary unit tests and integration tests.

Describe the solution you'd like

Ensure that unit tests and integration tests are executed for the latest push action on a pull request.
@eval-exec eval-exec added t:enhancement Type: Feature, refactoring. t:ci Type: CI labels Jan 30, 2024
@eval-exec eval-exec changed the title Prevent Addition of Pull Requests to Merge Queue without Passing Unit and Integration Tests Enforce the requirement for Pull Requests to pass both unit tests and integration tests before being added to the Merge Queue. Jan 30, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale To be closed due to a lack of activity label Jul 27, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Aug 1, 2024

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale To be closed due to a lack of activity t:ci Type: CI t:enhancement Type: Feature, refactoring.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eval-exec