User tests: Successful: Unsuccessful:
For staging as we won't use mozilla update the cacerts by using a github action once a month. This should mean we're never shipping with multiple years out of date files again. This should be fine as Mozilla's website notes:
We don't mind you downloading the PEM file from us in an automated fashion, but please don't do it more often than once per day. It is only updated once every few months anyway.
See https://github.com/wilsonge/joomla-cms/runs/2980634936?check_suite_focus=true for sample job output
Status | New | ⇒ | Pending |
Category | ⇒ | Repository |
Labels |
Added:
?
|
I dont want anything to auto commit to stuff 3.10-dev can we update this to create a PR similiar to the translation PR?
Labels |
Added:
?
Removed: ? |
Should be done but I don't have any easy way to test anymore :(
How could it be tested? Would merging it in help it to be tested? I have been told you can manually trigger gh actions too?
Btw it seems no user data has been added here can that be correct or is a default user from github used in that case?
Btw it seems no user data has been added here can that be correct or is a default user from github used in that case?
GitHub Actions have an auto-generated token that can be used for Pull Requests to the same repository
How could it be tested? Would merging it in help it to be tested? I have been told you can manually trigger gh actions too?
Yes once merge we can manually trigger and debug.
Status | Pending | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-09-20 10:44:34 |
Closed_By | ⇒ | zero-24 |
GitHub Actions have an auto-generated token that can be used for Pull Requests to the same repository
Cool :)
Yes once merge we can manually trigger and debug.
Merged ;)
Is there a way to test this on a modified branch where we have an outdated cert file so the auto commit has something to commit?