-
Notifications
You must be signed in to change notification settings - Fork 5
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
action to check patches #92
Conversation
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.
left me some notes for tomorrow
@@ -55,6 +49,3 @@ index 00000000..7d92a1c2 | |||
++-- |
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.
This looks odd, and should have been gone.
But maybe this is yet another level, I just have not cleaned up.
Cron trigger is in place for both actions. |
to match gluon style
a helper script, that refreshes the outer layer of site patches. Caliing it on a clean patchfolder does not invoke changes; hence, if calling it results in git changes, it is not clean.
Refreshed the patches, squashed intermediate commits and completed the list from above. |
This currently implements only the gluon part.
The outer parts of the site patches are not checked, but have been brought in the same format as the inner patches.
Whats left todo:
efresh-site-patches.sh
does not change anything, hence the patches are indeed in a clean statemake refresh-patches
in gluon (should have been done already and makes upstreaming patches easier)refresh-site-patches.sh
in this repo afterwords (should be done to make maintaining patches easier and clearer)Merging this will eventually resolve #83 and make submitting patches a little harder, but cleaner, so that reviewing patch PRs to this repo will become easier.
Furthermore it won't matter anymore, which OS we used to format the patch.