Skip to content

Commit ddb95ba

Browse files
committed
style: fix lint issues
Signed-off-by: Emilien Escalle <[email protected]>
1 parent cf555cf commit ddb95ba

File tree

9 files changed

+29
-6
lines changed

9 files changed

+29
-6
lines changed

.github/workflows/linter.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99
<!-- end badges -->
1010
<!-- start description -->
1111

12-
Reusable workflow that performs linting on the code base.
12+
Reusable workflow that performs linting on the codebase.
1313
Mainly using [Super-Linter](https://github.com/super-linter/super-linter), with some opinionated defaults.
1414

1515
<!-- end description -->

CONTRIBUTING.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ threatening, offensive, or harmful.
6565

6666
This Code of Conduct applies both within project spaces and in public spaces
6767
when an individual is representing the project or its community. Examples of
68-
representing a project or community include using an official project e-mail
68+
representing a project or community include using an official project email
6969
address, posting via an official social media account, or acting as an appointed
7070
representative at an online or offline event. Representation of a project may be
7171
further defined and clarified by project maintainers.

actions/checkout/README.md

+3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,9 @@
11
<!-- start branding -->
22
<!-- end branding -->
33
<!-- start title -->
4+
5+
# GitHub Action: Checkout
6+
47
<!-- end title -->
58
<!-- start badges -->
69
<!-- end badges -->

actions/create-and-merge-pull-request/README.md

+3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,9 @@
11
<!-- start branding -->
22
<!-- end branding -->
33
<!-- start title -->
4+
5+
# GitHub Action: Create and Merge Pull Request
6+
47
<!-- end title -->
58
<!-- start badges -->
69
<!-- end badges -->

actions/create-or-update-comment/README.md

+3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,9 @@
11
<!-- start branding -->
22
<!-- end branding -->
33
<!-- start title -->
4+
5+
# GitHub Action: Create or Update Comment
6+
47
<!-- end title -->
58
<!-- start badges -->
69
<!-- end badges -->

actions/get-github-actions-bot-user/README.md

+3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,9 @@
11
<!-- start branding -->
22
<!-- end branding -->
33
<!-- start title -->
4+
5+
# GitHub Action: Get GitHub Actions Bot User
6+
47
<!-- end title -->
58
<!-- start badges -->
69
<!-- end badges -->

actions/get-issue-number/README.md

+3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,9 @@
11
<!-- start branding -->
22
<!-- end branding -->
33
<!-- start title -->
4+
5+
# GitHub Action: Get Issue Number
6+
47
<!-- end title -->
58
<!-- start badges -->
69
<!-- end badges -->

actions/set-matrix-output/README.md

+9-4
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,9 @@
11
<!-- start branding -->
22
<!-- end branding -->
33
<!-- start title -->
4+
5+
# GitHub Action: Set Matrix Output
6+
47
<!-- end title -->
58
<!-- start badges -->
69
<!-- end badges -->
@@ -10,7 +13,9 @@ Set matrix ouput in file to be uploaded as artifacts, because GitHub action does
1013

1114
<!-- end description -->
1215

13-
The GitHub Actions workflow ensures artifact uniqueness by concatenating the workflow's `run_id`, `run_number`, and a user-provided `artifact-name`. Users can enhance this uniqueness by supplying a distinct `artifact-name` for each run, further ensuring that each artifact is uniquely identified across all runs and workflows. This strategy effectively prevents any clashes or overwrites, maintaining the integrity and traceability of artifacts, especially when multiple workflows are executed concurrently or under similar configurations.
16+
The GitHub Actions workflow ensures artifact uniqueness by concatenating the workflow's `run_id`, `run_number`, and a user-provided `artifact-name`.
17+
Users can enhance this uniqueness by supplying a distinct `artifact-name` for each run, further ensuring that each artifact is uniquely identified across all runs and workflows.
18+
This strategy effectively prevents any clashes or overwrites, maintaining the integrity and traceability of artifacts, especially when multiple workflows are executed concurrently or under similar configurations.
1419

1520
<!-- start contents -->
1621
<!-- end contents -->
@@ -37,9 +42,9 @@ The GitHub Actions workflow ensures artifact uniqueness by concatenating the wor
3742
<!-- end inputs -->
3843
<!-- start outputs -->
3944
40-
| **Output** | **Description** | **Default** | **Required** |
41-
| -------------------------- | ---------------------------------------------- | ------------------- | -------------------- |
42-
| <code>artifact-name</code> | The real unique name of the uploaded artifact. | undefined | undefined |
45+
| **Output** | **Description** | **Default** | **Required** |
46+
| -------------------------- | ---------------------------------------------- | ----------- | ------------ |
47+
| <code>artifact-name</code> | The real unique name of the uploaded artifact. | undefined | undefined |
4348
4449
<!-- end outputs -->
4550
<!-- start [.github/ghadocs/examples/] -->

actions/slugify/README.md

+3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,9 @@
11
<!-- start branding -->
22
<!-- end branding -->
33
<!-- start title -->
4+
5+
# GitHub Action: Slugify
6+
47
<!-- end title -->
58
<!-- start badges -->
69
<!-- end badges -->

0 commit comments

Comments
 (0)