Skip to content

Conversation

@christian-schilling
Copy link
Member

Instead of rejecting the whole push

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR changes the behavior of stacked push operations to skip commits without a Change-Id instead of rejecting the entire push with an error. When pushing to refs/stack/for/* or refs/for/*, commits without Change-Ids are now silently filtered out rather than causing a 500 Internal Server Error.

  • Removed error handling that rejected pushes containing commits without Change-Ids
  • Updated test expectations to reflect successful pushes (200 OK instead of 500 errors)
  • Commits without Change-Ids are now pushed to @heads namespace but skipped for @changes namespace

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
josh-core/src/changes.rs Removed the else branch that returned an error when a change has no id, allowing such changes to be filtered out instead
tests/proxy/push_stacked.t Updated test expectations to show successful push operations and correct ref updates for commits without Change-Ids
tests/proxy/push_stacked_gerrit.t Updated test expectations for Gerrit-style pushes to reflect the new skip behavior
tests/proxy/push_stacked_sub.t Updated test expectations for subdirectory pushes to show successful operations and additional git objects created

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@christian-schilling christian-schilling force-pushed the @changes/master/christian.schilling.de@gmail.com/stacked-skip branch 7 times, most recently from b9d666b to f0bec0b Compare November 13, 2025 17:47
Instead of rejecting the whole push
@christian-schilling christian-schilling force-pushed the @changes/master/christian.schilling.de@gmail.com/stacked-skip branch from f0bec0b to ef1b9ce Compare November 13, 2025 18:35
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.

2 participants