-
-
Notifications
You must be signed in to change notification settings - Fork 0
Updated to latest versions #55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| changelog: | ||
| exclude: | ||
| labels: | ||
| - question | ||
| - wontfix | ||
| - invalid | ||
| categories: | ||
| - title: Exciting New Features 🎉 | ||
| labels: | ||
| - enhancement | ||
| - feature | ||
| - title: Squashed Bugs 🐛 | ||
| labels: | ||
| - bug | ||
| - breaking-change | ||
| - title: Administrative | ||
| labels: | ||
| - administrative | ||
| - documentation | ||
| - dependencies | ||
| - title: Other Changes | ||
| labels: | ||
| - "*" |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -25,13 +25,13 @@ jobs: | |
| dotnet-version: 9.0.x | ||
|
|
||
| - name: Install GitVersion | ||
| run: dotnet tool install --global GitVersion.Tool --version 5.12.0 | ||
| uses: gittools/actions/gitversion/setup@v4.2.0 | ||
| with: | ||
| versionSpec: '6.4.0' | ||
|
|
||
| - name: Determine Version | ||
| id: gitversion | ||
| uses: gittools/actions/gitversion/execute@v0.10.2 | ||
| with: | ||
| useConfigFile: true | ||
| uses: gittools/actions/gitversion/execute@v4.2.0 | ||
|
Comment on lines
27
to
+34
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 Analysis chainScript executed: #!/bin/bash
# Find GitVersion configuration files in the repository
echo "=== Searching for GitVersion configuration files ==="
fd -e yml -e yaml | grep -iE 'gitversion|version' | head -20Repository: IowaComputerGurus/aspnetcore.utilities.fontawesometaghelpers <shell_result> stdout: </shell_result> Script executed: #!/bin/bash
# Check the content of GitVersion.yml
echo "=== GitVersion.yml content ==="
cat -n GitVersion.ymlRepository: IowaComputerGurus/aspnetcore.utilities.fontawesometaghelpers <shell_result> stdout: </shell_result> gittools/actions/gitversion execute v4.2.0 useConfigFile documentation <web_search_result>
Documentation / examples: GitTools actions examples for the execute step and the GitHub Actions example showing useConfigFile/configFilePath. [1][2] Sources: Citations:
useConfigFile: true is required for GitVersion.yml to be recognized by the new GitHub Actions. The web search confirms that Since your repository contains a GitVersion.yml file with critical configuration (ContinuousDeployment mode, branch-specific versioning rules, alpha labels), the removal of - name: Determine Version
id: gitversion
uses: gittools/actions/gitversion/execute@v4.2.0
with:
useConfigFile: trueWithout this, custom versioning logic will be lost and the build will use default GitVersion behavior instead. 🤖 Prompt for AI Agents |
||
|
|
||
| - name: Restore Packages | ||
| run: dotnet restore "${{ env.solution-path }}" | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,19 +1,19 @@ | ||
| mode: ContinuousDeployment | ||
| next-version: 1.0.0 | ||
| branches: | ||
| main: | ||
| regex: main | ||
| tag: 'alpha' | ||
| develop: | ||
| regex: develop | ||
| label: 'alpha' | ||
| increment: Patch | ||
| prevent-increment: | ||
| when-current-commit-tagged: true | ||
| source-branches: [] | ||
| pull-request: | ||
| regex: (pull|pull\-requests|pr)[/-] | ||
| tag: 'pr' | ||
| tag-number-pattern: '[/-](?<number>\d+)[-/]' | ||
| regex: ^(pull-requests|pull|pr)[\/-](?<Number>\d+) | ||
| label: 'pr{Number}' | ||
| increment: Patch | ||
| prevent-increment-of-merged-branch-version: false | ||
| is-release-branch: false | ||
| source-branches: [] | ||
| ignore: | ||
| sha: [] | ||
| merge-message-formats: {} | ||
| merge-message-formats: {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Script executed:
Repository: IowaComputerGurus/aspnetcore.utilities.fontawesometaghelpers
<shell_result>
Repository: IowaComputerGurus/aspnetcore.utilities.fontawesometaghelpers
Exit code: 0
stdout:
</shell_result>
Script executed:
Repository: IowaComputerGurus/aspnetcore.utilities.fontawesometaghelpers
<shell_result>
Repository: IowaComputerGurus/aspnetcore.utilities.fontawesometaghelpers
Exit code: 0
stdout:
</shell_result>
Script executed:
Repository: IowaComputerGurus/aspnetcore.utilities.fontawesometaghelpers
<shell_result>
Repository: IowaComputerGurus/aspnetcore.utilities.fontawesometaghelpers
Exit code: 0
stdout:
</shell_result>
Fix inconsistent SonarQube scanner parameters: use
sonar.tokenin both begin and end steps.The workflow uses
/d:sonar.tokenin the begin step (line 101) but/d:sonar.loginin the end step (line 105). Thesonar.loginparameter is deprecated; use/d:sonar.login="${{ env.SONAR_TOKEN }}"should be/d:sonar.token="${{ env.SONAR_TOKEN }}"to match the begin step and align with modern SonarQube/SonarCloud authentication standards.🤖 Prompt for AI Agents