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

[tests-only] [full-ci] Remove special files_primary_s3 guzzle code from CI #40150

Merged
merged 1 commit into from
Jun 20, 2022

Conversation

phil-davis
Copy link
Contributor

Description

These lines were added because the support for Guzzle7 in files_primary_s3 was in a branch called update-guzzle-6 (originally it was created before Guzzle7 was released). That PR owncloud/files_primary_s3#498 has now been merged to files_primary_s3 master. So we no longer need to checkout the special branch.

Related Issue

#39387

How Has This Been Tested?

CI

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Database schema changes (next release will require increase of minor version instead of patch)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Technical debt
  • Tests only (no source changes)

Checklist:

  • Code changes
  • Unit tests added
  • Acceptance tests added
  • Documentation ticket raised:
  • Changelog item, see TEMPLATE

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@phil-davis phil-davis merged commit 4596291 into master Jun 20, 2022
@delete-merged-branch delete-merged-branch bot deleted the remove-special-files_primary_s3-guzzle-ci branch June 20, 2022 03:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants