Skip to content

Create rule S8196: Single-method interface names should follow Go naming conventions #5757

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 5 commits into from
Nov 3, 2025
Merged

Create rule S8196: Single-method interface names should follow Go naming conventions #5757

merged 5 commits into from
Nov 3, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Oct 21, 2025

You can preview this rule here (updated a few minutes after each push).

Review

A dedicated reviewer checked the rule description successfully for:

  • logical errors and incorrect information
  • information gaps and missing content
  • text style and tone
  • PR summary and labels follow the guidelines

@github-actions github-actions bot added the go label Oct 21, 2025
@denis-troller denis-troller changed the title Create rule S8196 Create rule S8196: Single-method interface names should follow Go naming conventions Oct 21, 2025
@sonarqube-next
Copy link

sonarqube-next bot commented Oct 21, 2025

Quality Gate passed Quality Gate passed for 'rspec-frontend'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@sonarqube-next
Copy link

sonarqube-next bot commented Oct 21, 2025

Quality Gate passed Quality Gate passed for 'rspec-tools'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

sebastien-marichal
sebastien-marichal approved these changes Nov 3, 2025
View reviewed changes
Copy link
Contributor

@sebastien-marichal sebastien-marichal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@sonarqube-next
Copy link

sonarqube-next bot commented Nov 3, 2025

Quality Gate passed Quality Gate passed for 'rspec-frontend'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@sonarqube-next
Copy link

sonarqube-next bot commented Nov 3, 2025

Quality Gate passed Quality Gate passed for 'rspec-tools'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@sebastien-marichal sebastien-marichal marked this pull request as ready for review November 3, 2025 09:39
@sebastien-marichal sebastien-marichal added this pull request to the merge queue Nov 3, 2025
Merged via the queue into master with commit 71ba82d Nov 3, 2025
12 of 13 checks passed
@sebastien-marichal sebastien-marichal deleted the rule/add-RSPEC-S8196 branch November 3, 2025 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sebastien-marichal sebastien-marichal sebastien-marichal approved these changes

Assignees

@denis-troller denis-troller

Labels

go

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@sebastien-marichal @denis-troller @yassin-kammoun-sonarsource