Git filter-branch not filtering pull requests
up vote
0
down vote
favorite
I successfully used git filter-branch
(following the instructions here) to remove certain files from my repository. Upon inspection, it looks like they are completely gone from the commit history. However if I open up any of the previously closed pull requests, navigate to the commits and browse the repository at the time of the pull request, it looks like they are still there. Is there any way to rewrite the commit history of all pull requests (or even better: remove closed pull requests altogether)?
git github git-filter-branch
add a comment |
up vote
0
down vote
favorite
I successfully used git filter-branch
(following the instructions here) to remove certain files from my repository. Upon inspection, it looks like they are completely gone from the commit history. However if I open up any of the previously closed pull requests, navigate to the commits and browse the repository at the time of the pull request, it looks like they are still there. Is there any way to rewrite the commit history of all pull requests (or even better: remove closed pull requests altogether)?
git github git-filter-branch
1
the answer would probably depend on the server used.
– max630
Nov 19 at 18:10
I'm using github.com
– Floris
Nov 19 at 18:13
Pull requests are web-server add-ons, not part of Git itself, so it's not surprising that Git itself can't get rid of them either. GitHub in particular have a bunch of extra stuff they do that requires using their interfaces; I don't know if they have a way to clean out old pull requests other than deleting the repository entirely.
– torek
Nov 19 at 19:31
It seems so, after a bit of more searching I stumbled upon this question stackoverflow.com/questions/18318097/… which suggests it's not possible.
– Floris
Nov 19 at 20:19
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I successfully used git filter-branch
(following the instructions here) to remove certain files from my repository. Upon inspection, it looks like they are completely gone from the commit history. However if I open up any of the previously closed pull requests, navigate to the commits and browse the repository at the time of the pull request, it looks like they are still there. Is there any way to rewrite the commit history of all pull requests (or even better: remove closed pull requests altogether)?
git github git-filter-branch
I successfully used git filter-branch
(following the instructions here) to remove certain files from my repository. Upon inspection, it looks like they are completely gone from the commit history. However if I open up any of the previously closed pull requests, navigate to the commits and browse the repository at the time of the pull request, it looks like they are still there. Is there any way to rewrite the commit history of all pull requests (or even better: remove closed pull requests altogether)?
git github git-filter-branch
git github git-filter-branch
edited Nov 19 at 18:15
max630
5,12011339
5,12011339
asked Nov 19 at 18:01
Floris
1278
1278
1
the answer would probably depend on the server used.
– max630
Nov 19 at 18:10
I'm using github.com
– Floris
Nov 19 at 18:13
Pull requests are web-server add-ons, not part of Git itself, so it's not surprising that Git itself can't get rid of them either. GitHub in particular have a bunch of extra stuff they do that requires using their interfaces; I don't know if they have a way to clean out old pull requests other than deleting the repository entirely.
– torek
Nov 19 at 19:31
It seems so, after a bit of more searching I stumbled upon this question stackoverflow.com/questions/18318097/… which suggests it's not possible.
– Floris
Nov 19 at 20:19
add a comment |
1
the answer would probably depend on the server used.
– max630
Nov 19 at 18:10
I'm using github.com
– Floris
Nov 19 at 18:13
Pull requests are web-server add-ons, not part of Git itself, so it's not surprising that Git itself can't get rid of them either. GitHub in particular have a bunch of extra stuff they do that requires using their interfaces; I don't know if they have a way to clean out old pull requests other than deleting the repository entirely.
– torek
Nov 19 at 19:31
It seems so, after a bit of more searching I stumbled upon this question stackoverflow.com/questions/18318097/… which suggests it's not possible.
– Floris
Nov 19 at 20:19
1
1
the answer would probably depend on the server used.
– max630
Nov 19 at 18:10
the answer would probably depend on the server used.
– max630
Nov 19 at 18:10
I'm using github.com
– Floris
Nov 19 at 18:13
I'm using github.com
– Floris
Nov 19 at 18:13
Pull requests are web-server add-ons, not part of Git itself, so it's not surprising that Git itself can't get rid of them either. GitHub in particular have a bunch of extra stuff they do that requires using their interfaces; I don't know if they have a way to clean out old pull requests other than deleting the repository entirely.
– torek
Nov 19 at 19:31
Pull requests are web-server add-ons, not part of Git itself, so it's not surprising that Git itself can't get rid of them either. GitHub in particular have a bunch of extra stuff they do that requires using their interfaces; I don't know if they have a way to clean out old pull requests other than deleting the repository entirely.
– torek
Nov 19 at 19:31
It seems so, after a bit of more searching I stumbled upon this question stackoverflow.com/questions/18318097/… which suggests it's not possible.
– Floris
Nov 19 at 20:19
It seems so, after a bit of more searching I stumbled upon this question stackoverflow.com/questions/18318097/… which suggests it's not possible.
– Floris
Nov 19 at 20:19
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53380284%2fgit-filter-branch-not-filtering-pull-requests%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
the answer would probably depend on the server used.
– max630
Nov 19 at 18:10
I'm using github.com
– Floris
Nov 19 at 18:13
Pull requests are web-server add-ons, not part of Git itself, so it's not surprising that Git itself can't get rid of them either. GitHub in particular have a bunch of extra stuff they do that requires using their interfaces; I don't know if they have a way to clean out old pull requests other than deleting the repository entirely.
– torek
Nov 19 at 19:31
It seems so, after a bit of more searching I stumbled upon this question stackoverflow.com/questions/18318097/… which suggests it's not possible.
– Floris
Nov 19 at 20:19