Skip to content

Update PR validation workflow #177

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

Merged
merged 3 commits into from
Jul 24, 2025
Merged

Update PR validation workflow #177

merged 3 commits into from
Jul 24, 2025

Conversation

devcrocod
Copy link
Contributor

Update validation-pr. Added more events to start validation

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@devcrocod devcrocod requested review from sdubov and tiginamaria July 21, 2025 09:21
@devcrocod devcrocod enabled auto-merge (squash) July 24, 2025 07:43
@devcrocod devcrocod force-pushed the devcrocod/update-validate branch from bc572c8 to 0ce08a8 Compare July 24, 2025 08:39
@devcrocod devcrocod merged commit e5214fe into main Jul 24, 2025
2 of 3 checks passed
@devcrocod devcrocod deleted the devcrocod/update-validate branch July 24, 2025 08:45
skarpovdev pushed a commit to skarpovdev/kotlin-sdk that referenced this pull request Aug 5, 2025
* Update PR validation workflow

* Update PR validation trigger configuration

* Add concurrency control to PR validation workflow
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants