Sonarqube versions

[ivanmolodec]

Доработана установка версий проекта в SonarQube, добавлено описание принципа установки версий конфигурации

Summary by CodeRabbit

• Documentation

  • Updated guidelines for managing configuration versions in the README.md.
  • Added rules for version increments based on change types, including build, version, and sub-edition criteria.
  • Emphasized the importance of versioning for releases and SonarQube analysis.

• Chores

  • Enhanced SonarQube workflow to extract and use the configuration version for project analysis.

[coderabbitai]

Walkthrough

The recent changes focus on enhancing the versioning system of the project by introducing rules for managing configuration versions. These changes are reflected in both the project's workflow and the README file, ensuring consistent versioning for releases and SonarQube analysis. The modifications involve extracting the version from a configuration file and emphasizing structured version increments based on the type of changes made.

Changes

File(s)	Change Summary
.github/workflows/sonar.yml	Added a step to extract the version from a configuration file and utilized this version in the SonarQube project analysis.
README.md	Introduced rules for managing configuration versions, detailed version increment guidelines, and emphasized the importance of versioning for releases and SonarQube analysis.

A swish and a hop, a step we make,
Versions evolve with each change we stake.
Every pull request, a build anew,
With structure and care, our project grew.
Configuration rules now in line,
For a future bright and so divine! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f14f735 and 1bd450c.

Files selected for processing (2)

• .github/workflows/sonar.yml (3 hunks)
• README.md (1 hunks)

Additional context used

Markdownlint

README.md

36-36: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines

---

37-37: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines

Additional comments not posted (1)

.github/workflows/sonar.yml (1)

39-39: LGTM! Dynamic version integration in SonarQube analysis.

The use of dynamic project versioning for SonarQube analysis ensures that each analysis accurately reflects the current state of the project.

[sonar-openbsl-ru-qa-bot]

Analysis Details

0 Issues

• 0 Bugs
• 0 Vulnerabilities
• 0 Code Smells

Coverage and Duplications

• No coverage information (0.00% Estimated after merge)
• No duplication information (0.50% Estimated after merge)

Project ID: PSSL

View in SonarQube

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1bd450c and 5713aeb.

Files selected for processing (1)

• README.md (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• README.md