Commit ID is not included in review request if --include is used on rbt post.
Review Request #5818 — Created May 13, 2014 and submitted
Previously when --include was used on an rbt post, it would take the
commit ID of the current commit. The issue is that if someone
uploaded multiple files from the same commit separately, the
identical commit IDs would cause conflicts in the ReviewRequests. The
solution is to not include the commit ID when "--include" is used on
an rbt post.
Made a commit with two files in the change. I was able to post and
publish both without error, which would not happen normally. When
looking on the review board web ui, there was no commit id
associated with either.
Description | From | Last Updated |
---|---|---|
I'd love to see a comment explaining why we do this. |
david |
MA
- Change Summary:
-
Added comments to change.
- Commit:
-
59a875d28e267309ee70e974c83650cc9a32103c7557d0472a637d200974e471c2e359457d229603
- Diff:
-
Revision 2 (+6)
-
This is a review from Review Bot. Tool: PEP8 Style Checker Processed Files: rbtools/commands/post.py Ignored Files: