Request changes on PR

I reviewed the diff and found failing tests and a missing changelog entry. Request changes from Maya and cc the release manager, Jason, so she fixes the test and adds the changelog before I re-run CI. Tell Maya which test suite failed, where the assertion broke, and the exact wording the changelog should include.

Before I send the review to the repo maintainers, make it easy for Maya to act: surface the failing test name and the stack frame line, show the minimal code change that would fix the assertion, and draft one clear changelog sentence that matches our release notes tone. Flag any potential backwards-incompatible behavior.

I just posted a request changes review on Priya’s branch for the failing integration test and the missing changelog; CI reran and still fails the same suite. Priya is responsive but new to this repo. I’m worried requesting more changes will stall the release and approving will ship a flaky test. What likely caused the recurring failure and what is the best next move I should take now to keep the release date and protect quality?

Over the last three sprints we keep sending PRs back because the integration test flaky in payment-service keeps failing and contributors omit changelog entries. I own release coordination. Where am I losing time and credibility, and which habit should I change first so fewer PRs return for the same reasons?