MNT Run module-standardiser

This commit is contained in:
Steve Boyd 2024-05-16 10:16:12 +12:00
parent 4dcd1883eb
commit dd17c2e55f
3 changed files with 13 additions and 32 deletions

View File

@ -1,9 +1,11 @@
name: Dispatch CI name: Dispatch CI
on: on:
# At 4:00 PM and 5:00 PM # At 4:20 PM UTC, only on Friday and Saturday
schedule: schedule:
- cron: '0 16,17 * * *' - cron: '20 16 * * 5,6'
permissions: {}
jobs: jobs:
dispatch-ci: dispatch-ci:
@ -11,6 +13,9 @@ jobs:
# Only run cron on the silverstripe account # Only run cron on the silverstripe account
if: (github.event_name == 'schedule' && github.repository_owner == 'silverstripe') || (github.event_name != 'schedule') if: (github.event_name == 'schedule' && github.repository_owner == 'silverstripe') || (github.event_name != 'schedule')
runs-on: ubuntu-latest runs-on: ubuntu-latest
permissions:
contents: read
actions: write
steps: steps:
- name: Dispatch CI - name: Dispatch CI
uses: silverstripe/gha-dispatch-ci@v1 uses: silverstripe/gha-dispatch-ci@v1

View File

@ -1,17 +1,21 @@
name: Keepalive name: Keepalive
on: on:
# At 1:05 PM UTC, on day 22 of the month # At 4:20 PM UTC, on day 13 of the month
schedule: schedule:
- cron: '5 13 22 * *' - cron: '20 16 13 * *'
workflow_dispatch: workflow_dispatch:
permissions: {}
jobs: jobs:
keepalive: keepalive:
name: Keepalive name: Keepalive
# Only run cron on the silverstripe account # Only run cron on the silverstripe account
if: (github.event_name == 'schedule' && github.repository_owner == 'silverstripe') || (github.event_name != 'schedule') if: (github.event_name == 'schedule' && github.repository_owner == 'silverstripe') || (github.event_name != 'schedule')
runs-on: ubuntu-latest runs-on: ubuntu-latest
permissions:
actions: write
steps: steps:
- name: Keepalive - name: Keepalive
uses: silverstripe/gha-keepalive@v1 uses: silverstripe/gha-keepalive@v1

View File

@ -1,28 +0,0 @@
# Contributing
Any open source product is only as good as the community behind it. You can participate by sharing code, ideas, or simply helping others. No matter what your skill level is, every contribution counts. See our [high level contribution overview](http://silverstripe.org/contributing-to-silverstripe) on silverstripe.org on how you can help out.
## Bugtracker ##
Bugs are tracked on [github.com](https://github.com/silverstripe/framework/issues).
Please read our [issue reporting guidelines](http://doc.silverstripe.org/framework/en/misc/contributing/issues).
## Development and Contribution ##
For submitting patches, please read our [guide to contributing code](https://docs.silverstripe.org/en/5/contributing/code/). We only accept pull requests on github.com.
## Links ##
* [Server Requirements](http://doc.silverstripe.org/framework/en/installation/server-requirements)
* [Changelogs](http://doc.silverstripe.org/framework/en/changelogs/)
* [Bugtracker: Framework](https://github.com/silverstripe/silverstripe-framework/issues)
* [Bugtracker: CMS](https://github.com/silverstripe/silverstripe-cms/issues)
* [Bugtracker: Installer](https://github.com/silverstripe/silverstripe-installer/issues)
* [Forums](http://silverstripe.org/forums)
* [Developer Mailinglist](https://groups.google.com/forum/#!forum/silverstripe-dev)
## Copyright
**IMPORTANT: By supplying code to the SilverStripe core team in patches, tickets and pull requests, you agree to assign copyright of that code to SilverStripe Limited, on the condition that SilverStripe Limited releases that code under the BSD license.**
We ask for this so that the ownership in the license is clear and unambiguous, and so that community involvement doesn't stop us from being able to continue supporting these projects. By releasing this code under a permissive license, this copyright assignment won't prevent you from using the code in any way you see fit.