ci: Basic continuous integration workflow#2
Merged
OS-pedrogustavobilro merged 3 commits intomainfrom Mar 10, 2026
Merged
Conversation
Without this build fails. Was also missing from mono-repo copy commit because that file was in root
Brought from monorepo, also present in some other plugins.
OS-pedrogustavobilro
requested review from
OS-ruimoreiramendes,
alexgerardojacinto and
andredestro
andredestro
approved these changes
Mar 9, 2026
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
2 participants
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.
Description
This PR adds a workflow to run continuous integration on PRs, as well as on pushes to specific branches from which releases may be cut in the future.
Also fixed an issue in
mainthat would have been caught with CI.I'm not adding the full extent of workflows we have in other plugins like filesystem, specifically npm release, maven central / CocoaPods Trunk releases, as I think that can go in separate PR(s).
Change Type
Rationale / Problems Fixed
Basically making sure that whatever PRs are opened in the future, have at least some validations in place.