Skip to content
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

Add a branch-restore.sh script for restoring branches after accidental deletion #30976

Closed
wants to merge 1 commit into from

Conversation

grahamc
Copy link
Member

@grahamc grahamc commented Oct 30, 2017

It has happened a few times that branches get accidentally deleted in
mass. This script pushes all branches that are known to be at origin
and pushes them back to origin.

…l deletion

It has happened a few times that branches get accidentally deleted in
mass. This script pushes all branches that are known to be at `origin`
and pushes them back to `origin`.
@orivej
Copy link
Contributor

orivej commented Oct 30, 2017

That checkout is inconvenient. I came up with this (--dry-run for testing):

git fetch origin

git for-each-ref refs/remotes/origin --format 'branch=%(refname:lstrip=3)' --shell |
    while read entry; do
        eval "$entry"
        if [ "$branch" != HEAD ] && [ "$branch" != master ]; then
           git push --dry-run origin "refs/remotes/origin/$branch:refs/heads/$branch"
        fi
    done

@grahamc
Copy link
Member Author

grahamc commented Nov 30, 2018

@GrahamcOfBorg build hello php fizzbuzz

@grahamc
Copy link
Member Author

grahamc commented Nov 30, 2018

@GrahamcOfBorg build help

@mmahut
Copy link
Member

mmahut commented Aug 12, 2019

Are there any updates on this pull request, please?

@stale
Copy link

stale bot commented Jun 1, 2020

Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:

  1. Search for maintainers and people that previously touched the
    related code and @ mention them in a comment.
  2. Ask on the NixOS Discourse. 3. Ask on the #nixos channel on
    irc.freenode.net.

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 1, 2020
@domenkozar domenkozar closed this Jul 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants