Revamp CSV validation process in GitHub workflow #15
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
added 2 commits
March 13, 2024 03:38
This commit overhauls the CSV validation process in the GitHub workflow. The previous setup process was replaced with a new one focussed on validating CSV files using the 'jbzoo/csv-blueprint' library. Specifically, this involved checking for both valid and invalid CSV files and generating various reports based on the validation results. The commit also updates the README file with more detailed plans and ideas.
Pull Request Test Coverage Report for Build 8260770563Details
💛 - Coveralls |
added 5 commits
March 13, 2024 03:44
Expanded upon the GitHub Actions workflow for Docker releases. Added steps to checkout, tag Docker images based on various attributes, and established QEMU and Docker Buildx. Also introduced a conditional login to Docker Hub, specifically to avoid logging in during pull requests.
Simplified the base images for Docker tags by removing redundancy. Switched from multi-line to single-line image specification. Previous tagging strategy dependent on various events/attributes is streamlined to only associate Docker tags based on branch, pull request and semantic versions. This simplifies the release process.
The wording in the README.md file's checklist has been simplified for clarity. The changes are particularly focused on the sections about batch processing, release workflow, and performance optimization. The new wording makes it easier to understand each item on the checklist, improving the documentation for developers and users.
The commit refactors the usage of actions/checkout in multiple parts of the demo.yml workflow, removing the redundant 'fetch-depth: 0' attribute for code simplification. Secondly, it resolves potential file path conflicts by updating the locations where CSV files are accessed in various steps, aiming at error prevention during runtime.
This commit removes "via GA" from the job name in demo.yml to keep it generic. Additionally, it widens the scope of trigger branches in release-docker.yml to include all ones with any types of names; previously, it was limited to branches with certain naming conventions only.
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.
No description provided.