3 ms·
I just used this on my repo and that's exactly what it did. It created a PR. I then reviewed the PR, squashed the commits down to a single one and merged it. I
by colinbartlett 12y ago
I just used this on my repo and that's exactly what it did. It created a PR. I then reviewed the PR, squashed the commits down to a single one and merged it.
It worked beautifully. 10/10 would use again.
- jrochkind1 12y agoSweet, this is much better, and a perfect use of PRs. I wonder if it needs to ask for github 'write' permissions in order to do this, or if it could be changed to just ask for read permission and make PRs? If Githubs permissions don't work that way, they should be fixed -- if they do, this tool should be fixed. When I logged in via oath or whatever, Github warns: > This application will be able to read and write all public and private repo data. This includes the following: > Code; Issues; Pull requests; ... Yeah, I don't really wanna do that. Granting a random third-party else permission to commit to all of your repos, public and private?