-
Notifications
You must be signed in to change notification settings - Fork 44
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
v1: include compose_id in clone response #870
Conversation
Can one of the admins verify this patch? |
This PR is stale because it has been open 30 days with no activity. Remove "Stale" label or comment or this will be closed in 7 days. |
168a0ae
to
0b9d70f
Compare
81d605a
to
8d7e48e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
380a116
to
14ce777
Compare
00e9d5a
to
c76df9d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
🍏 🎉 |
@ezr-ondrej ugh I didn't press the button ._. can you rebase, happy to ack again |
Clones should include their parent ID, to easily match them. It follows the rest guidelines to be traversable.
c76df9d
to
94d1de7
Compare
Sure :) here it goes! :) |
/retest |
🍏 🎉 |
Clones should include their parent ID, to easily match them.
This follows rest standards.
I've got no idea how to do this properly, but I just felt it would be really nice to have compose_id in the clone detail response 🤔