OpenTTD-patches/.dorpsgek.yml

notifications:
  global:
    irc:
      - openttd
      - openttd.notice

  push:
    only:
    - master
    only-by:
    - DorpsGek
  commit-comment:
  discussion:
  pull-request:
  issue:
  tag-created:
  workflow-run:
    only:
    - .github/workflows/release.yml
    - .github/workflows/ci-nightly.yml
Add: notify IRC about pushes to this repository 2018-08-04 18:53:17 +00:00			`notifications:`
Fix: [DorpsGek] don't report all pushes, but just those done by DorpsGek Those are most often the translator updates, which are pushed directly to master (and not via a Pull Request). 2019-08-31 22:45:45 +00:00			`global:`
Add: notify IRC about pushes to this repository 2018-08-04 18:53:17 +00:00			`irc:`
			`- openttd`
			`- openttd.notice`
Fix: [DorpsGek] don't report all pushes, but just those done by DorpsGek Those are most often the translator updates, which are pushed directly to master (and not via a Pull Request). 2019-08-31 22:45:45 +00:00
			`push:`
			`only:`
			`- master`
			`only-by:`
			`- DorpsGek`
Add: [DorpsGek] also announce comments on commits 2019-09-04 17:46:44 +00:00			`commit-comment:`
Change: [DorpsGek] also announce Discussion creation/comments from GitHub (#8991) 2021-04-10 09:47:17 +00:00			`discussion:`
Add: notify IRC about pull-requests and issues 2018-08-05 15:19:41 +00:00			`pull-request:`
			`issue:`
Add: [DorpsGek] announce new tags on IRC (#7931) 2020-01-12 16:01:17 +00:00			`tag-created:`
Codechange: [DorpsGek] announce failures in nightlies to IRC / Discord (#12256) 2024-03-10 13:22:15 +00:00			`workflow-run:`
			`only:`
			`- .github/workflows/release.yml`
Codechange: [CI] build some targets every night, instead of every PR This mainly as they are not expected to fail, or give more information than the other targets already would. And this is just hogging up the CI pipeline. On average, these targets take ~80 CPU-minutes to finish. 2024-03-10 09:48:11 +00:00			`- .github/workflows/ci-nightly.yml`