-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub integration #119
Comments
Out of curiosity: why do we want this? |
Mostly to integrate GitHub checks with mailing list workflows, where patch application would be done with GitHub to ensure that checks gate the application. I am not planning to do it immediately, but I am opening the issue as a "reminder that it can be done". |
Okay. We already pushes tags to github so checks can happen there, I'm not sure what more pull requests can provide. We do want some webhook callback mechanism to get the results, though. For now we'll have to "poll" from the testing script, to get results. |
Can you see the results of checks that are run on a tag? Pull requests would provide the UI for checks and for merging, basically. (Laszlo asked what can be done to integrate GitHub CI with mailing list workflow). |
That is a good point. It's not easy afaict. |
Also, since Patchew can parse the MAINTAINERS file, it could use that to assign reviewers on GitHub (e.g. |
Write a new plugin that creates a pull request for every complete series, and closes it when the series is merged. The plugin could also use the GitHub webhook to mark series as merged/obsolete when a pull request is closed, and to report the state of GitHub checks as a status box.
The text was updated successfully, but these errors were encountered: