summaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
2021-01-02Codechange: Drop libxdg-basedir dependency in favour of finding the ↵Charles Pigott
directories ourselves
2020-12-26Fix: [Actions] cmakeBuildType is only used with CMakeListsTxtBasic (#8435)Patric Stout
We use CMakeListsTxtAdvanced, and as such, we have to do this our self via "-DCMAKE_BUILD_TYPE=RelWithDebInfo". Otherwise we are producing Debug builds instead of Release builds. Oops.
2020-12-22Add: [GitHub] PR template. (#8414)frosch
2020-12-19Add: [Actions] release workflow for both releases and nightliesPatric Stout
This has several ways of being triggered: - When creating a new release via the GitHub interface. Fully automated that will produce new binaries, upload them, and it will even update the website to tell about the new version. - When triggered in an automated way from OpenTTD/workflows to start a nightly. - Manually via the Release workflow, which accepts branches, Pull Requests and tags to build. Rerunning a job is safe and should be without issues. Everything retriggers and updates what-ever might have been broken. In fact, except for dates, it should produce identical results. Co-authored-by: Charles Pigott <charlespigott@googlemail.com>
2020-12-15Add: [Actions] preview workflow, where PRs can be reviewed in the browserPatric Stout
When a developer attaches the "preview" label, a build is created and published on https://preview.openttd.org/. After that, new pushes to the PR are automatically build (as long as the "preview" label exists). If a non-developer attaches the "preview" label, it will be removed.
2020-12-15Add: support for emscripten (play-OpenTTD-in-the-browser)Patric Stout
Emscripten compiles to WASM, which can be loaded via HTML / JavaScript. This allows you to play OpenTTD inside a browser. Co-authored-by: milek7 <me@milek7.pl>
2020-12-13Fix: [Actions] cleanup ci-build workflow to be up-to-date (#8375)Patric Stout
Also, while at it, make it more like the upcoming release-workflow, so they look a lot more similar. Functional it should be the same, except that Windows should now also output when a test fails.
2020-12-10Fix: Prevent infinite recursion in commit checkerglx22
2020-10-10Fix: [Actions] Call apt-get update before trying to install packagesCharles Pigott
2020-10-10Add: [Actions] Add problem matchers for CI platformsCharles Pigott
2020-10-03Add: [Actions] CI build workflowglx
2020-01-19Add: [Actions] commit-checker workflowglx
2019-08-31Add: [GitHub] sponsor button on github.com (#7700)Roger
2019-01-29Add: [GitHub] Add issue template to encourage better issue reporting. (#7137)PeterN
2019-01-24Add: [GitHub] enable probot/stale, to flush out stale issues/pull requestsPatric Stout
Stale bot checks if an issue hasn't had any attention in the last 60 days, or if a pull request hasn't had any attention in the last 30 days. If so, it marks it as stale. After 7 more days, it closes the issue/pull request. Any activity on the issue/pull request resets the timer. This helps keeping the counter low, and the work manageable. There is a lot of reasoning behind this idea, and other projects show it really helps to keep the issue/pull request count low. More information here: https://github.com/probot/stale
generated by cgit v1.2.3-70-g09d2 (git 2.47.0) at 2024-11-30 20:15:46 +0000