Bug Fix for Merging "reenhanced:master" instead of "master"#171
Conversation
88bfa1b to
773b689
Compare
|
@codenamev Apologies for sending another diff, but I found a bug last minute when trying to I am also adding |
9606856 to
6f39718
Compare
|
Can you update the tests please? I have another branch ( |
|
The tests are passing as I didn't add any additional methods or complex There was no added functionality so I don't believe new tests need to be On Friday, May 13, 2016, Valentino notifications@github.com wrote:
|
|
@codenamev do you mind patching in my changes and seeing if the issues that you saw still exist? I believe this patch will solve the clean up and deliver issues that were present. |
|
The tests are there for quality assurance that the methods do what they say. Since we have restructured so much here, it's possible that the old tests didn't cover the new way of doing things. We'll want to first add failing tests to catch the issue you found so that we can ensure any new changes going forward don't affect it as well. Also, we have a running PR open doing some cleanup before we can release. It turns out that the squash feature in the API is only in preview and requires special headers to access. While we can simple add those headers in, the |
6f39718 to
65ab40b
Compare
|
@codenamev I updated the tests. |
|
It looks like the bug in question is using a new syntax for the branch name |
|
@codenamev Perhaps I misunderstood you? The checkout and some cleanup commands that were ran after I just checked locally both with force delivering and normally, each with and without cleanup. All 4 test cases work locally and the test coverage reflects this as well. Please let me know if we can merge this. This solves an immediate problem with cleanup / deploy. |
65ab40b to
65d8c8d
Compare
| unless feature_branch_name.index(':').nil? | ||
| feature = feature_branch_name[(feature_branch_name.index(':') + 1)..-1] | ||
| end | ||
| self.base_branch_name = self.base_branch_name[/[^:]+$/] |
There was a problem hiding this comment.
why do we need to check for :?
There was a problem hiding this comment.
@codenamev Line 180 is the same logic as what I am trying to do previously in line 180 - 186. This is just a bit more elegant Ruby Regex Syntax to match the expression in the string after the ":" to the end and if ":" does not exist, simply match the whole string.
There are 2 cases:
"master" => "master"
"codenamev:master" => "master"
Regex supports both (And it is a single line of Ruby code). ^_^
There was a problem hiding this comment.
Ah, I wasn't aware that Github or Bitbucket formatted the head/base labels like that. Let's move this into the GitHub::PullRequest#initialize and BitBucket::PullRequest#initialize methods. We should be able to trust a consistent format wherever else we need to reference these.
65d8c8d to
84cb534
Compare
|
The additional tests make sure that each command that was supposed to run executed on the correct |
84cb534 to
2a746a8
Compare
|
lgtm, thank you 😄 |
2a746a8 to
3646ef2
Compare
|
@codenamev np, lets merge this! |
No description provided.