0

I need to PR my branch again or in other words re-run my PR commit. Build failed and it was because the branch name itself was upper case and was sending that as part of an S3 bucket name when sending a call to the S3 API. So I need to kinda revert it, commit a toLower in my code, and re-pr the branch.

Is this possible?

Another option would be to rename the branch itself to lower-case..same text.

Dark Matter
  • 29
  • 2
  • 9

1 Answers1

1

Instead of revert use git commit --amend or rebase and update the branch with force-pushing.

phd
  • 82,685
  • 13
  • 120
  • 165
  • can I do just a git commit then force? How will that trigger a "pr" commit rather than a regular commit though? Travis needs to rebuild and set the feature branch value and in order to do that you have to PR a branch – Dark Matter Jun 22 '17 at 05:54
  • also I want my commit message to be a bulleted list of items that I did, how can I do that? – Dark Matter Jun 22 '17 at 05:55
  • I just did a commit then force push for now, I have an old commit that keeps causing merge conflicts when I try to rebase and I can't get around it. I try to skip that commit during rebase but it doesn't let me. – Dark Matter Jun 22 '17 at 06:15
  • 1. You don't need forced push after a regular commit. You only need it after commit editing. There is no such thing as "PR" commits; commits are added to an existing PR when you push the branch that is PR'd. 2 [Bulleted lists — help at Github](https://help.github.com/articles/basic-writing-and-formatting-syntax/#lists). – phd Jun 22 '17 at 09:43
  • no I did a force commit when the branch was still in PR state – Dark Matter Jun 27 '17 at 21:26
  • Amend, rebase, filter-branch. In strict sense these are not editing because commits are nver changed — instead, git creates new commits and move branch pointer. This branch moving is exactly the cause for forced push. – phd Jun 27 '17 at 21:54