Closed cordoval closed 10 years ago
so we would find a conflict status information in the github api and show that on the dashboard? sounds awesome!
the idea is even to have a batch job that reruns gush something so that it rebases the Pr automatically if it is a clean rebase, if not it sends an email notification of the sort. Maybe is a combined effort.
the dashboard so far was only about showing information, not actively trying to change things on github.
i would rather not push to github from the dashboard, or even check out the project. what if gush gets this feature, and then the dashboard can be enabled to trigger this gush operation if it finds conflicted pull requests?
the triggering would come from the dashboard then? isn't that the same? or you want gush to read the db of dashboard to check where the conflicted PRs are and batch them to run a rebase on them?
i think the dashboard should process the information and display it. and when it detects a conflict, it could call gush when enabled, to try to fix the situation.
you are right, i think this needs to be in gush and triggered by dashboard, hmm i bet api has a listing for https://github.com/pulls so cycling over those and launching an attack on those rebasing jobs is the way to go. Closing to first resolve it in gush land.
thanks good brainstorming :+1:
https://github.com/gushphp/gush/issues/326
i think this feature is better suit for this project so moving it here