Skip to content

Instantly share code, notes, and snippets.

@dm7

dm7/README.md

Forked from robertpainsi/README.md
Created December 10, 2019 10:16
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save dm7/7ffca7034b44a8f5a972bd5c25bdaf28 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save dm7/7ffca7034b44a8f5a972bd5c25bdaf28 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. @robertpainsi robertpainsi revised this gist Jul 2, 2017. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,3 +1,5 @@
    ### How to reopen a pull-request after a force-push?

    #### Precodinitions
    * You need the rights to reopen pull requests on the repository.
    * The pull request hasn't been merged, just closed.
  2. @robertpainsi robertpainsi revised this gist Jul 2, 2017. 1 changed file with 4 additions and 2 deletions.
    6 changes: 4 additions & 2 deletions README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,6 +1,8 @@
    You need the rights to reopen pull requests on the repository.
    Merged pull-requests _can't_ be reopened. Only _closed but not merged_ pull-requests can.
    #### Precodinitions
    * You need the rights to reopen pull requests on the repository.
    * The pull request hasn't been merged, just closed.

    #### Instructions
    1. Write down the current commit hash of your PR-branch `git log --oneline -1 <PR-BRANCH>`
    2. Write down the latest commit hash on github before the PR has been closed.
    3. `git push -f origin <GITHUB-HASH-FROM-STEP-2>:<PR-BRANCH>`
  3. @robertpainsi robertpainsi revised this gist Jul 2, 2017. 1 changed file with 1 addition and 0 deletions.
    1 change: 1 addition & 0 deletions README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,5 @@
    You need the rights to reopen pull requests on the repository.
    Merged pull-requests _can't_ be reopened. Only _closed but not merged_ pull-requests can.

    1. Write down the current commit hash of your PR-branch `git log --oneline -1 <PR-BRANCH>`
    2. Write down the latest commit hash on github before the PR has been closed.
  4. @robertpainsi robertpainsi revised this gist May 3, 2017. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -7,7 +7,7 @@ You need the rights to reopen pull requests on the repository.
    5. `git push -f origin <HASH-FROM-STEP-1>:<PR-BRANCH>`

    #### Example
    We've a PR branch `my-feature` currently at `1234567`. Looking at the the PRs page, we see that the PR was closed when `my-feature` pointed at `0abcdef`.
    You've a PR branch `my-feature` currently at `1234567`. Looking at the the PRs page, we see that the PR was closed when `my-feature` pointed at `0abcdef`.
    * `git push -f origin 0abcdef:my-feature` `#pushing the old commit the PR has been closed with`
    * Reopen the PR.
    * `git push -f origin 1234567:my-feature` `#pushing the latest commit`
  5. @robertpainsi robertpainsi revised this gist May 2, 2017. 1 changed file with 1 addition and 2 deletions.
    3 changes: 1 addition & 2 deletions README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,3 @@
    ### Introduction
    You need the rights to reopen pull requests on the repository.

    1. Write down the current commit hash of your PR-branch `git log --oneline -1 <PR-BRANCH>`
    @@ -7,7 +6,7 @@ You need the rights to reopen pull requests on the repository.
    4. Reopen the PR.
    5. `git push -f origin <HASH-FROM-STEP-1>:<PR-BRANCH>`

    ### Example
    #### Example
    We've a PR branch `my-feature` currently at `1234567`. Looking at the the PRs page, we see that the PR was closed when `my-feature` pointed at `0abcdef`.
    * `git push -f origin 0abcdef:my-feature` `#pushing the old commit the PR has been closed with`
    * Reopen the PR.
  6. @robertpainsi robertpainsi revised this gist May 2, 2017. 1 changed file with 9 additions and 2 deletions.
    11 changes: 9 additions & 2 deletions README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,7 +1,14 @@
    ### Introduction
    You need the rights to reopen pull requests on the repository.

    1. Write down the current commit hash of your PR-branch `git log --oneline -1 <PR-BRANCH>`
    2. Write down the latest commit hash on github before the PR has been closed.
    3. git push -f origin `<GITHUB-HASH-FROM-STEP-2>:<PR-BRANCH>`
    3. `git push -f origin <GITHUB-HASH-FROM-STEP-2>:<PR-BRANCH>`
    4. Reopen the PR.
    5. `git push -f origin <HASH-FROM-STEP-1>:<PR-BRANCH>`
    5. `git push -f origin <HASH-FROM-STEP-1>:<PR-BRANCH>`

    ### Example
    We've a PR branch `my-feature` currently at `1234567`. Looking at the the PRs page, we see that the PR was closed when `my-feature` pointed at `0abcdef`.
    * `git push -f origin 0abcdef:my-feature` `#pushing the old commit the PR has been closed with`
    * Reopen the PR.
    * `git push -f origin 1234567:my-feature` `#pushing the latest commit`
  7. @robertpainsi robertpainsi revised this gist Jun 28, 2016. 1 changed file with 3 additions and 3 deletions.
    6 changes: 3 additions & 3 deletions README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,7 +1,7 @@
    You need the rights to reopen pull requests on the repository.

    1. Write down the current commit hash of your PR-branch (git log --oneline -1 <PR-BRANCH>)
    1. Write down the current commit hash of your PR-branch `git log --oneline -1 <PR-BRANCH>`
    2. Write down the latest commit hash on github before the PR has been closed.
    3. git push -f origin <GITHUB-HASH-FROM-STEP-2>:<PR-BRANCH>
    3. git push -f origin `<GITHUB-HASH-FROM-STEP-2>:<PR-BRANCH>`
    4. Reopen the PR.
    5. git push -f origin <HASH-FROM-STEP-1>:<PR-BRANCH>
    5. `git push -f origin <HASH-FROM-STEP-1>:<PR-BRANCH>`
  8. @robertpainsi robertpainsi created this gist Jun 28, 2016.
    7 changes: 7 additions & 0 deletions README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,7 @@
    You need the rights to reopen pull requests on the repository.

    1. Write down the current commit hash of your PR-branch (git log --oneline -1 <PR-BRANCH>)
    2. Write down the latest commit hash on github before the PR has been closed.
    3. git push -f origin <GITHUB-HASH-FROM-STEP-2>:<PR-BRANCH>
    4. Reopen the PR.
    5. git push -f origin <HASH-FROM-STEP-1>:<PR-BRANCH>