Initial release #7
Merged
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
Initial solution and tests
- Include workflow to publish packages
* feat: Added SqlServerClientSpark * fix: PR CI job simplified name
Simplified the base condition in the GitHub Actions workflow. Previously, it was checking if the event name is 'pull_request', which was unnecessary. Now, it directly uses github.ref without any conditional checks. This makes the code cleaner and easier to understand.
- Un-commented the 'with' section under the gitversion execution step in the GitHub workflow. - Added 'additionalArguments: '/showConfig'' to display configuration details during runtime.
- Added overrideConfig to the GitVersion step in the GitHub Actions workflow, specifying tags for 'develop' and 'hotfix' branches. - Modified git tagging process to prefix version number with a 'v', aligning with semantic versioning standards.
- Disabled the 'showConfig' argument in gitversion execution - Added a new tag 'rc' under release in the overrideConfig section
- Switched from hardcoded branch configurations to using a config file - Expanded and detailed the GitVersion.yaml file for better version control - Changed versioning scheme to MajorMinorPatch - Enabled commit-message-incrementing feature - Added specific rules for each type of branch (develop, main, release, feature, pull-request, hotfix, support) - Updated mode to ContinuousDelivery for most branches
- Modified the git tag and push commands in the GitHub workflow to include 'version/' prefix - Updated the tag-prefix in GitVersion.yaml to match new tagging scheme
- Reorganized the trigger paths under a single 'build' category in the GitHub workflow - Added conditional checks to only run build steps if changes are detected in relevant files - Ensured test-reporter only runs when there are changes requiring a build, instead of always running - Streamlined artifact gathering and uploading by adding conditional checks for changes requiring a build
- Updated the conditional statements in the GitHub workflow file to correctly reference the `change_detection` step. - This change affects all tasks that rely on this condition, ensuring they only run when changes are detected. - The affected tasks include dotnet installation, gitversion setup and execution, nuget caching, dotnet restore/build/test operations, test reporting, and artifact gathering/uploading.
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.