Source Babelforce: Migrate to manifest-only#43439
Merged
Natik Gadzhi (natikgadzhi) merged 2 commits intomasterfrom Aug 9, 2024
Merged
Source Babelforce: Migrate to manifest-only#43439Natik Gadzhi (natikgadzhi) merged 2 commits intomasterfrom
Natik Gadzhi (natikgadzhi) merged 2 commits intomasterfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Natik Gadzhi (natikgadzhi)
approved these changes
Aug 9, 2024
Louis Auneau (LouisAuneau)
pushed a commit
to LouisAuneau/airbyte
that referenced
this pull request
Aug 13, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Migrates source-babelforce to manifest-only format
How
Ran the airbyte-ci commands [
migrate-to-manifest-only,bump-version,format fix]Review Guide
4.3.0and contain an inline specmanifest-onlylanguage tag and point to a recent version ofsource-declarative-manifestmanifest.yamlfor the spec testUser Impact
None
Can this PR be safely reverted and rolled back?