Split repository's CI workflow into functional parts. #3
Conversation
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
In the experimental repository the action was migrated from, the system was to have a single workflow for each action hosted in the repository. Although it is a sensible approach in that context, it meant combining things that are only loosely related into a single workflow. Now that the action has a dedicated repository, it makes sense to split it into multiple workflows.
Codecov Report
@@ Coverage Diff @@
## main #3 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 2 2
Lines 1555 1555
=========================================
Hits 1555 1555 Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
In the experimental repository the action was migrated from, the system was to have a single workflow for each action hosted in the repository.
Although it is a sensible approach in that context, it meant combining things that are only loosely related into a single workflow. Now that the action has a dedicated repository, it makes sense to split it into multiple workflows: