-
Notifications
You must be signed in to change notification settings - Fork 7
Bump guibranco/github-csharpier-linter-action from 1.0.16 to 1.0.18 #296
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
Bump guibranco/github-csharpier-linter-action from 1.0.16 to 1.0.18 #296
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
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.
Automatically approved by gstraccini[bot]
|
Here's the code health analysis summary for commits Analysis Summary
Code Coverage Report
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
|
@dependabot squash and merge |
|
Beginning January 27, 2026, Dependabot will no longer support the @dependabot squash and merge command. Please use GitHub's native pull request controls instead. Please see the changelog announcement for additional details. |
|
Bumps [guibranco/github-csharpier-linter-action](https://github.com/guibranco/github-csharpier-linter-action) from 1.0.16 to 1.0.18. - [Release notes](https://github.com/guibranco/github-csharpier-linter-action/releases) - [Commits](guibranco/github-csharpier-linter-action@v1.0.16...v1.0.18) --- updated-dependencies: - dependency-name: guibranco/github-csharpier-linter-action dependency-version: 1.0.18 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dbbea59 to
1df690c
Compare
|
One of your CI runs failed on this pull request, so Dependabot won't merge it. Dependabot will still automatically merge this pull request if you amend it and your tests pass. |



Bumps guibranco/github-csharpier-linter-action from 1.0.16 to 1.0.18.
Release notes
Sourced from guibranco/github-csharpier-linter-action's releases.
Commits
7a96a32Toggle makeLatest flag in CI workflow56799bbUpdate ci.yml (#35)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot will merge this PR once CI passes on it, as requested by @guibranco.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Description by Korbit AI
What change is being made?
Update the GitHub workflow to use guibranco/[email protected] instead of v1.0.16.
Why are these changes being made?
Apply a newer action release to bring in fixes/updates and keep the linter integration current; no functional changes expected beyond the upgrade.