PR#507: Suggest a way to track remote branch in the error log -

rpkg

#507 Suggest a way to track remote branch in the error log

Merged Jun 9, 2020 by onosek. Opened Jun 5, 2020 by cqi.

cqi/rpkg more-info-in-log into master

Download 507.patch

cqi commented Jun 5, 2020

Signed-off-by: Chenxiong Qi cqi@redhat.com

cqi commented Jun 5, 2020

Hi, the idea of this change comes from CLOUDBLD-1294.

onosek commented Jun 9, 2020

Commit bc25c7f3 fixes this pull-request

Pull-Request has been merged by onosek

Jun 9, 2020

onosek commented Jun 9, 2020

Thanks, I have just amended JIRA ticket to the commit.

cqi commented Jun 11, 2020

@onosek Thank you very much.

ktdreyer commented Jun 16, 2020

"If this branch should track a remote branch, fix it with this command:"

... and we should interpolate "BRANCHNAME" with the localbranch variable since we have that right here. That will make it easy for the user to copy-and-paste.

onosek commented Jun 16, 2020

@ktdreyer @cqi
Is it better now? https://pagure.io/rpkg/pull-request/508

Metadata

Assignee

None

Tags

No Tags

rpkg

#507 Suggest a way to track remote branch in the error log Merged Jun 9, 2020 by onosek. Opened Jun 5, 2020 by cqi. cqi/rpkg more-info-in-log into master

Metadata

#507 Suggest a way to track remote branch in the error log

Merged Jun 9, 2020 by onosek. Opened Jun 5, 2020 by cqi.

cqi/rpkg more-info-in-log into master