-
Notifications
You must be signed in to change notification settings - Fork 25
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
Issue #224 #238
Issue #224 #238
Conversation
Current Aviator status
This PR was merged using Aviator.
See the real-time status of this PR on the
Aviator webapp.
Use the Aviator Chrome Extension
to see the status of your PR within GitHub.
|
FlexReview SummaryBased on the code complexity and the author's expertise score, these are the suggested reviewers:
See the list of alternate reviewers in the detailed breakdown below. Detailed BreakdownAuthor’s expertise score for the modified files:
† Indicates that the file doesn't need an expert review. (?) See full breakdown of the reviewers on the Aviator webapp. |
cmd/av/commit_amend.go
Outdated
@@ -75,6 +75,10 @@ var commitAmendCmd = &cobra.Command{ | |||
|
|||
branchesToSync := meta.SubsequentBranches(tx, currentBranchName) | |||
|
|||
// issue #224: |
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.
Remove this line.
Thank you for review! |
/aviator merge |
Aviator has accepted the merge request. It will enter the queue when all of the required status checks have passed. Aviator will update the sticky status comment as the pull request moves through the queue. |
Hi, this issue (#224) is a "good first issue", so I tried to address it
Is my change what this issue aims to address? I'd appreciate clarification of the details if my understanding is incorrect.
Thank you.