Skip to content

fix: test PR - #119

Closed
yvasyliev wants to merge 16 commits into
feature/v3from
feature/v3-pr-label
Closed

fix: test PR#119
yvasyliev wants to merge 16 commits into
feature/v3from
feature/v3-pr-label

Conversation

@yvasyliev

Copy link
Copy Markdown
Owner

Description

Please provide a clear and concise description of your changes.

Related Issue

Closes #[issue-number] (if applicable)

Type of Change

  • Bug fix
  • New feature
  • Documentation update
  • Refactoring
  • Other (please describe):

Checklist

  • My code follows the project’s code style and conventions
  • I have added or updated Javadoc for public classes and methods
  • I have added or updated unit tests as needed
  • All tests pass locally (./gradlew build or gradlew.bat build on Windows)
  • I have not committed any secrets (passwords, API keys, etc.)

How Has This Been Tested?

Please describe the tests you ran to verify your changes.

Additional Information

Add any other context or screenshots about the pull request here.

@yvasyliev yvasyliev changed the title feat: test PR feat: test PR1 Apr 5, 2026
@yvasyliev yvasyliev changed the title feat: test PR1 feat: test PR Apr 5, 2026
@github-actions github-actions Bot added the feat New feature label Apr 5, 2026
@yvasyliev yvasyliev changed the title feat: test PR fix: test PR Apr 5, 2026
@github-actions github-actions Bot added fix Bugfix and removed feat New feature labels Apr 5, 2026
@yvasyliev yvasyliev changed the title fix: test PR fixed: test PR Apr 5, 2026
@yvasyliev yvasyliev changed the title fixed: test PR fixed: test PR1 Apr 5, 2026
@github-actions

github-actions Bot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

👋 Hey @yvasyliev, it looks like the PR title doesn't follow the Conventional Commits format.

While it's not a blocker for this PR, following the conventional commits format helps us to automatically calculate next release version, categorize changes and generate changelog.

Good candidates might be feat: fixed: test PR1 or fix: fixed: test PR1. You can also add ! to indicate a breaking change, e.g. feat!: fixed: test PR1.

Please follow the Conventional Commits for more details and examples. 🙌

@yvasyliev yvasyliev changed the title fixed: test PR1 chore: test PR1 Apr 5, 2026
@github-actions

github-actions Bot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

👋 Hey @yvasyliev, it looks like the PR title doesn't follow the Conventional Commits format.

While it's not a blocker for this PR, following the conventional commits format helps us to automatically calculate next release version, categorize changes and generate changelog.

Good candidates might be feat: chore: test PR1 or fix: chore: test PR1. You can also add ! to indicate a breaking change, e.g. feat!: chore: test PR1.

Please follow the Conventional Commits for more details and examples. 🙌

@yvasyliev yvasyliev changed the title chore: test PR1 chore: test PR Apr 5, 2026
@yvasyliev yvasyliev changed the title chore: test PR chore: test PR1 Apr 5, 2026
@yvasyliev yvasyliev changed the title chore: test PR1 chore: test PR Apr 5, 2026
@yvasyliev yvasyliev changed the title chore: test PR chore: test PR1 Apr 5, 2026
@github-actions github-actions Bot removed the fix Bugfix label Apr 5, 2026
@yvasyliev yvasyliev changed the title chore: test PR1 feat: test PR1 Apr 5, 2026
@yvasyliev yvasyliev changed the title feat: test PR1 feat: test PR Apr 5, 2026
@yvasyliev yvasyliev changed the title feat: test PR test PR Apr 5, 2026
@github-actions github-actions Bot removed the feature label Apr 5, 2026
@yvasyliev yvasyliev changed the title test PR test PR1 Apr 5, 2026
@yvasyliev yvasyliev changed the title test PR1 test PR Apr 5, 2026
@yvasyliev yvasyliev changed the title test PR fix: test PR Apr 5, 2026
@github-actions github-actions Bot added the fix Bugfix label Apr 5, 2026
@yvasyliev yvasyliev closed this Apr 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fix Bugfix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant