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

Fix stuck/broken CI #2032

Merged
merged 5 commits into from
Nov 7, 2023
Merged

Fix stuck/broken CI #2032

merged 5 commits into from
Nov 7, 2023

Conversation

strickvl
Copy link
Contributor

@strickvl strickvl commented Nov 7, 2023

(for testing CI w/r/t linting which is failing on client.py)

Pre-requisites

Please ensure you have done the following:

  • I have read the CONTRIBUTING.md document.
  • If my change requires a change to docs, I have updated the documentation accordingly.
  • If I have added an integration, I have updated the integrations table and the corresponding website section.
  • I have added tests to cover my changes.
  • I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Other (add details above)

@strickvl strickvl requested a review from avishniakov November 7, 2023 16:24
@strickvl strickvl changed the title Fix broken CI Fix stuck/broken CI Nov 7, 2023
@strickvl strickvl added the internal To filter out internal PRs and issues label Nov 7, 2023
@strickvl strickvl merged commit 6ed7136 into develop Nov 7, 2023
29 checks passed
@strickvl strickvl deleted the bugfix/broken-ci-client-linting branch November 7, 2023 23:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal To filter out internal PRs and issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants