Pull Request: Add Option for Building a Specific Package #34
Conversation
This file contains 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.
Summary
This PR adds an option to the GitHub Actions workflow for building a specific package within the repository. Previously, the CI process would build all packages, but with this update, users can now specify a particular package to be built. This enhancement provides more flexibility and efficiency, especially when only one package requires testing or development, reducing overall build times and resource consumption.
Changes
Updated the GitHub Actions workflow to include an input parameter for selecting a specific package.
Modified the CI logic to conditionally build the selected package if specified.
Fallback to building all packages if no specific package is provided.
Benefits
Faster build times when only one package needs to be tested.
Reduces resource usage by skipping unnecessary builds of unrelated packages.
Simplifies the development and testing process for contributors focusing on a single package.
Testing
Verified that the workflow correctly builds only the specified package.
Confirmed that the workflow defaults to building all packages when no package is specified.