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
Add a patch breakage checker to continuous build #225
base: main
Are you sure you want to change the base?
Conversation
On the build below, you see the "Patch Compatibility" at work on the 6th line. I will try rebasing some patches in the meantime. |
Since cirrus-ci is often crowded and somewhat slow, can we get the same as a Github action? That would avoid any outside dependencies. |
My, my! It IS a Github action. I first tried as a Cirrus build, not sure why, I'm new to CI. |
I think for a start: yes, please, move the repo into notqmail. But I dislike the "notqmail-patch" name, this can be understood as if it does something entirely different. How about "brokemaster" then? |
Back to it after a long while. |
b7391ec
to
3d756e3
Compare
That looks like running to completion. We are good now, ready for review. Let's see how it turns out in practice? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but I suggest also renaming the name of the workflow to "brokemaster" or something like that as well. Also please add a symlink to autobuilds/
.
3d756e3
to
09afd64
Compare
After too long, the suggested changes are completed. |
I propose to move my https://github.com/josuah/notqmail-patch to https://github.com/notqmail/notqmail-patch (or any better name), so that anyone allowed to alter notqmail can also alter notqmail-patch.
Then, what about this to check for patch compatiblity ?
This also lets us maintain adapted versions of the patches, and adapt them as we break them.
In the end, some way for us to keep patches going as we move things around.