Commit Graph

12 Commits

Author SHA1 Message Date
Denis Buzdalov
87bdf0ba23 [ ci ] Bump deprecated versions of used CI actions to avoid warnings 2024-01-31 17:18:24 +03:00
Mathew Polzin
e9464848c0
CI Maintenance (#2855)
* rename and clarify 'previous version' setting.

* bump GitHub Action versions.

* make initialise direct dependency of any stage that relies on it for conditional logic.

* turn nix step back on and update cachix action.

* I think pinning a version should not really help here anymore. also, nix-flakes-installer no longer exists.
2023-01-18 09:54:42 -06:00
CodingCellist
59460c2f46
[ admin ] Update CHANGELOG and CONTRIBUTORS (#2703)
* [ admin ] Update CHANGELOG and CONTRIBUTORS

We really need to do a release at some point...

* [ ci ] Don't check capitalised proper names in links and code

Sometimes hyperlinks and code-blocks just don't use the "proper"
capitalisation (e.g. `.html` vs `.HTML`), and that's okay.
(or even critical as links may not be found without "incorrect" format)

* [ ci ] Don't check terminology in links and code-blocks

Hopefully this is the right fix for the problem in #2703

* [ ci ] 3rd attempt at fixing nl linter

* [ ci ] Attempt no. 4 at fixing nl linter

* [ ci ] Point NL linter at YAML config file

Was that actually it??

* Update CHANGELOG.md

* Add note about forward declaration of records

* [ admin ] Add PR template with CHANGELOG reminder

To hopefully help mitigate big crawl-throughs of what's changed,
à la #2703.

* [ admin ] Reflow CHANGELOG to 80 characters where possible

Only done for the "next version" changes for the sake of diff size.
(Personally, I'd want to have the linter enforce this, but that might be
too extreme; there's already a note in the CI config complaining about
line length...)

* [ admin ] Make linter happy

It never ends...

Co-authored-by: Joel Berkeley <16429957+joelberkeley@users.noreply.github.com>
Co-authored-by: Steve Dunham <dunhamsteve@gmail.com>
2022-10-21 16:48:37 +02:00
Attila Lendvai
4a75d71c02 [ ci ] update previous version to v0.5.1, and super-linter to v4.8.5
The current super-linter v3 line is broken due to a failed backport,
they recommend to use the v4 line:
https://github.com/github/super-linter/issues/2253

Pick a specific version, so that such transient linter bugs won't
camouflage as Idris CI failures.
2021-12-27 18:04:25 -08:00
Mathew Polzin
523c0a6d78 actually, with the change to the super linter, there's really no point in having CI work on both master and main at the same time, we just need to rename the branch right away for a smooth transition. 2021-07-22 13:42:45 +01:00
Mathew Polzin
7c85971698 Make sure main branch is covered in addition to master during the transition. Make the default branch for linting the main branch. 2021-07-22 13:42:45 +01:00
Stiopa Koltsov
855ee3cbd0 Ignore @generated in super-linter
Super-linter supports it now
2021-06-28 17:26:32 +01:00
Robert Wright
1e15ff31d3 Disable C file linting 2021-05-20 14:25:16 +01:00
Mathew Polzin
9f8a8b5d76
Add a total way of reading files in. (#1070) 2021-02-18 11:13:25 +00:00
Stiopa Koltsov
e6447e7515 Check docs in CI 2021-02-04 14:59:14 +00:00
Stiopa Koltsov
cffade6bf8 Run super-linter in all branches
Use the same trigger as in the rest of jobs.

Before submitting a PR, commit is pushed to a private branch where
the jobs are executed. Super-linter should be executed in these
jobs as well to get signal about linting issue before submitting a
PR, to reduce noise to PR reviewers.
2021-02-04 14:52:49 +00:00
Stiopa Koltsov
68eecce0f4 Add super-linter
Example run with error:
[here](https://github.com/stepancheg/Idris2/runs/1718861440?check_suite_focus=true)

The downside is super-linter runs for 3 minutes. But that's probably expected
since the linter is [provided by GitHub](https://github.com/github/super-linter).

Two days ago when I submitted #931 I did not know super-linter exists.
2021-01-21 11:31:35 +00:00