Skip to content
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

Disabling breaking changes check on main #13283

Merged

Conversation

peternied
Copy link
Member

@peternied peternied commented Apr 18, 2024

Description

There have been a couple of cases where changes have come into OpenSearch's main branch that are intentionally modifying the @publicapi annotated classes. While it is useful to have a signal about breaking changes, it is important that minimal noise is generated.

Until we have a clear plan for how to create a strong signal for breaking changes on main by disabling this workflow.

Related Issues

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
  • Commits are signed per the DCO using --signoff
  • Commit changes are listed out in CHANGELOG.md file (See: Changelog)
  • Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Peter Nied <peternied@hotmail.com>

This comment was marked as resolved.

Copy link
Contributor

✅ Gradle check result for fdf9191: SUCCESS

@reta reta merged commit ba25c23 into opensearch-project:main Apr 18, 2024
39 of 41 checks passed
@peternied peternied deleted the disable-breaking-change-check-on-main branch April 18, 2024 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants