aboutsummaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
2024-02-05Use new GitHub issue templates (#5900)Orestis Floros
Biggest benefit is that the users are presented with a set of editable fields instead of having to edit markdown directly in a text box, which is less friendly. Links to userguide and IPC docs are clickable in the description. See https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
2023-09-21Update to clang-format-15Orestis Floros
2023-09-05Update to actions/checkout@v4 (#5653)Orestis Floros
Update to [actions/checkout@v4](https://github.com/actions/checkout/releases/tag/v4.0.0) According to https://github.com/actions/checkout/issues/1448 it might fix the issue we are encountering. Even if it doesn't, no apparent harm from using the latest version.
2023-04-11GH Actions: Check for gcc before deploying (#5483)Orestis Floros
Fixes #5482
2023-04-02Update ubuntu & clang-format in builds (#5467)Orestis Floros
2023-01-23GitHub Actions: revert changes and use `if` on each step (#5393)Orestis Floros
2023-01-23Actions: Fix BASENAME env vars (#5392)Orestis Floros
2023-01-23GitHub Actions: push artifacts only on next branch (#5388)Orestis Floros
2023-01-19Bump -D_FORTIFY_SOURCE=2 to -D_FORTIFY_SOURCE=3 (#5379)Michael Stapelberg
Arch Linux is discussing increasing to 3, so we should probably keep up: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/17
2023-01-02GitHub Actions: remove i386 autobuild packages (#5345)Michael Stapelberg
They are newly failing since the previous commit (upgrading to Ubuntu focal), so instead of debugging what the issue is, let’s just remove them entirely. Not many i386 users are left, as the world is on amd64 and arm64 these days.
2023-01-02GitHub Actions: switch to meson setup subcommandMichael Stapelberg
Using “meson” instead of “meson setup” results in a warning.
2023-01-02GitHub Actions: build with -D_FORTIFY_SOURCE=2Michael Stapelberg
This requires --buildtype=debugoptimized (or --buildtype=release, but optimizations need to be enabled), and will allow us to keep the i3 build free of warnings during development. Distributions like Debian build with -D_FORTIFY_SOURCE=2.
2022-12-06Update to clang-format-12 (as 10 is no longer installable) (#5317)Michael Stapelberg
No changes to the code are needed.
2022-10-24Update actions/checkout to v3 (#5226)Orestis Floros
Fixes #5225
2022-09-21GitHub Actions: skip build + test steps in meson dist (#5148)Michael Stapelberg
Originally I thought we should remove the build and test steps in favor of the “meson dist” step. But, then we lose verbose build command lines and access to the test logs, and having the failing test logs readily available is critical. So, instead, let’s make the “meson dist” step not repeat the work that was already done in earlier steps. The Meson manual even documents the --no-tests flag precisely for our use case: > The meson dist command has a --no-tests option to skip build and tests steps > of generated packages. It can be used to not waste time for example when done > in CI that already does its own testing. From https://mesonbuild.com/Creating-releases.html fixes https://github.com/i3/i3/issues/5145
2021-11-05Move clang-format, safe-wrappers, release notes check in new jobOrestis Floros
Benefits: - Faster feedback in case of error - More checks run in parallel - Removes stuff from Dockerfiles - Uses newest available clang-format (in ubuntu repos)
2021-11-05Keep each release note in a single fileOrestis Floros
To avoid annoying merge conflicts. Perl script is provided for convenience and simple format checking in PRs.
2021-09-10Add option to start a new discussion in the templatesOrestis Floros
2021-09-08GH actions: Archive complete logs on test failureOrestis Floros
https://docs.github.com/en/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy > By default, the artifacts and log files generated by workflows are > retained for 90 days before they are automatically deleted.
2021-05-23switch from Travis to GitHub actions for continuous integration (CI) (#4428)Michael Stapelberg
2020-12-29Update CONTRIBUTING and issue template(s) for feature requestsIngo Bürk
2020-05-06hacking-howto: Add warningOrestis Floros
2020-05-01Merge pull request #4050 from orestisfl/config-details-bug-templateIngo Bürk
Bug template: Add collapsible for config file
2020-04-30Add RELEASE-NOTES for next release (#4046)Orestis Floros
* Add RELEASE-NOTES template for next The placeholder items are useful instead of having to find the • character for every new release. Closes #4040 * Remove leftover bugfix release notes from tree
2020-04-30Bug template: Add collapsible for config fileOrestis Floros
As discussed in #4022
2018-10-07add specific GitHub issue templatesMichael Stapelberg
I learnt about this from the GitHub blog: https://blog.github.com/2018-05-02-issue-template-improvements/
2018-07-12Fix ISSUE_TEMPLATE typoOrestis Floros
2018-05-20Updated ISSUE_TEMPLATE.md (#3295)Ingo Bürk
2017-09-24Replace http:// with https:// where applicableMichael Stapelberg
The testcases will be updated automatically in a separate commit.
2017-02-06document our project governance model (#2675)Michael Stapelberg
2017-01-03.github/CONTRIBUTING.md: explain that compositors are unsupported (#2621)Michael Stapelberg
2016-02-19Add issue templateMichael Stapelberg
This is a mix of what our old new-ticket-form used to suggest: http://code.stapelberg.de/git/i3-new-ticket/tree/templates/index.html …and what CONTRIBUTING.md already entailed. See https://github.com/blog/2111-issue-and-pull-request-templates
2016-02-19move CONTRIBUTING.md to .github/ directoryMichael Stapelberg
See https://github.com/blog/2111-issue-and-pull-request-templates
7apu2bq3rhoylwmucxizk54afw5jyda7pho4j5zdcqpwkufke7zdzwad.onion