{"action":"created","issue":{"url":"https://api.github.com/repos/rebase-helper/rebase-helper/issues/462","repository_url":"https://api.github.com/repos/rebase-helper/rebase-helper","labels_url":"https://api.github.com/repos/rebase-helper/rebase-helper/issues/462/labels{/name}","comments_url":"https://api.github.com/repos/rebase-helper/rebase-helper/issues/462/comments","events_url":"https://api.github.com/repos/rebase-helper/rebase-helper/issues/462/events","html_url":"https://github.com/rebase-helper/rebase-helper/issues/462","id":303066826,"number":462,"title":"RFE: complete automation","user":{"login":"TomasTomecek","id":1662493,"avatar_url":"https://avatars0.githubusercontent.com/u/1662493?v=4","gravatar_id":"","url":"https://api.github.com/users/TomasTomecek","html_url":"https://github.com/TomasTomecek","followers_url":"https://api.github.com/users/TomasTomecek/followers","following_url":"https://api.github.com/users/TomasTomecek/following{/other_user}","gists_url":"https://api.github.com/users/TomasTomecek/gists{/gist_id}","starred_url":"https://api.github.com/users/TomasTomecek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/TomasTomecek/subscriptions","organizations_url":"https://api.github.com/users/TomasTomecek/orgs","repos_url":"https://api.github.com/users/TomasTomecek/repos","events_url":"https://api.github.com/users/TomasTomecek/events{/privacy}","received_events_url":"https://api.github.com/users/TomasTomecek/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-07T11:44:56Z","updated_at":"2018-03-07T12:19:25Z","closed_at":null,"author_association":"NONE","body":"Thank you for making rebase-helper awesome. I absolutely love that tool and it saves me so much time.\r\n\r\nI have an idea how to make it even better (sorry if there is an issue for that already).\r\n\r\nWhat if rebase-helper would cover **every** manual task a maintainer needs to do?\r\n\r\nHere is how I use rebase-helper now:\r\n\r\n1. I run `rebase-helper x.y.z`.\r\n2. If the build succeeds, I copy the rebased sources to the dist-git repo.\r\n3. I run `fedpkg new-sources`.\r\n4. I create a new commit.\r\n5. I push the changes.\r\n6. I build.\r\n\r\nWhat I would love to see rebase-helper doing is:\r\n\r\n1. I run `rebase-helper x.y.z`\r\n\r\nAnd it performs all the things mentioned in points 2 up to 6."},"comment":{"url":"https://api.github.com/repos/rebase-helper/rebase-helper/issues/comments/371121197","html_url":"https://github.com/rebase-helper/rebase-helper/issues/462#issuecomment-371121197","issue_url":"https://api.github.com/repos/rebase-helper/rebase-helper/issues/462","id":371121197,"user":{"login":"skisela","id":26842433,"avatar_url":"https://avatars0.githubusercontent.com/u/26842433?v=4","gravatar_id":"","url":"https://api.github.com/users/skisela","html_url":"https://github.com/skisela","followers_url":"https://api.github.com/users/skisela/followers","following_url":"https://api.github.com/users/skisela/following{/other_user}","gists_url":"https://api.github.com/users/skisela/gists{/gist_id}","starred_url":"https://api.github.com/users/skisela/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/skisela/subscriptions","organizations_url":"https://api.github.com/users/skisela/orgs","repos_url":"https://api.github.com/users/skisela/repos","events_url":"https://api.github.com/users/skisela/events{/privacy}","received_events_url":"https://api.github.com/users/skisela/received_events","type":"User","site_admin":false},"created_at":"2018-03-07T12:19:25Z","updated_at":"2018-03-07T12:19:25Z","author_association":"COLLABORATOR","body":"@TomasTomecek Thanks for feedback and ideas!\r\n\r\nYou are right at the time all the steps are needed, except `step 2` might be exchanged by applying the generated `changes.patch` in `rebase-helper-results` directory.\r\n\r\nYour idea is something we are trying to achieve. To be more exact, we were thinking of using the generated changes to create a pull request, which would trigger CI tests (if any are present) and then be accepted by the maintainer.\r\n\r\nThe same approach will likely be used for automatic rebases, which are momentarily disabled.\r\n\r\nI think that would be ideal, as in case of modifying patches during the rebase, some bugs might be introduced, which should be revealed immediately after."}}
{"actor":{"display_login":"skisela"}}