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

Update timeout for .github/workflows/test-pr.yaml #224

Closed
wants to merge 2 commits into from

Conversation

team-eng-enablement
Copy link
Collaborator

This is an automated pull request to update default timeouts for all jobs in .github/workflows/test-pr.yaml that do not currently contain a default timeout property.

Please review these changes closely to ensure that all jobs have sufficient time to run. If a job needs more time, please add a timeout property to that job to override the organization default.

Additionally, please be attentive to unintended changes to the workflow YAML file, as the parser is not perfect.

Lastly, note that it is up to the reviewer to merge this pull request and delete the PR branch once they are satisfied with the changes.

@team-eng-enablement team-eng-enablement requested a review from a team as a code owner February 3, 2024 12:15
@CLAassistant
Copy link

CLAassistant commented Feb 3, 2024

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ programmer04
❌ team-eng-enablement
You have signed the CLA already but the status is still pending? Let us recheck it.

@programmer04 programmer04 enabled auto-merge (squash) May 10, 2024 09:39
auto-merge was automatically disabled May 14, 2024 14:10

Pull request was closed

@programmer04 programmer04 deleted the chore/update-timeouts-test-pr.yaml branch May 14, 2024 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants