Brett Randall

The error message is fairly clear - Stash won't let you push refs under "pull-requests". There's a few things you could do, including renaming that branch in your local, making...

It looks like a hook, pre-receive hook, is declining the push, but may be doing-so silently. You need to establish why that hook is rejecting the pushes to those refs,...

I recommend: - web search of that error message and go through the list of possible causes - checking the Stash server logs - contacting Atlassian support

If you need to delete Pull Requests (and their hidden branches) permanently (because they contain history you want to delete), you have to contact GitHub Support with that request.

@RWOverdijk did you rewrite a repo cloned from GitHub, including pull-requests, and try and push that rewritten history back, to GitHub? That's what a lot of the issues in this...

Interesting. Perhaps GitHub opened this up? To confirm beyond doubt you'd need to: - have a GitHub repo with Pull Requests with history that will be rewritten - clone the...

> No (open) push requests, only 1 additional branch - so it should be very simply, isn't it? I think you mean Pull Requests. You are distinguishing open PRs from...

See also #143 for an useful test on the limitations of glob expansion by Git itself in `.gitignore` and `.gitattributes`.

Non-bare repos are typically clones - working copies. A hosted/shared Git repo is typically bare.

Size is the minimum size for which all smaller content is valid, not bulk/junk, and should not be deleted.