Skip to content

Commit

Permalink
style: fix lint issues
Browse files Browse the repository at this point in the history
Signed-off-by: Emilien Escalle <[email protected]>
  • Loading branch information
neilime committed Feb 23, 2024
1 parent cf555cf commit ddb95ba
Show file tree
Hide file tree
Showing 9 changed files with 29 additions and 6 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/linter.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
<!-- end badges -->
<!-- start description -->

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

<!-- end description -->
Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ threatening, offensive, or harmful.

This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
representing a project or community include using an official project email
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.
Expand Down
3 changes: 3 additions & 0 deletions actions/checkout/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
<!-- start branding -->
<!-- end branding -->
<!-- start title -->

# GitHub Action: Checkout

<!-- end title -->
<!-- start badges -->
<!-- end badges -->
Expand Down
3 changes: 3 additions & 0 deletions actions/create-and-merge-pull-request/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
<!-- start branding -->
<!-- end branding -->
<!-- start title -->

# GitHub Action: Create and Merge Pull Request

<!-- end title -->
<!-- start badges -->
<!-- end badges -->
Expand Down
3 changes: 3 additions & 0 deletions actions/create-or-update-comment/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
<!-- start branding -->
<!-- end branding -->
<!-- start title -->

# GitHub Action: Create or Update Comment

<!-- end title -->
<!-- start badges -->
<!-- end badges -->
Expand Down
3 changes: 3 additions & 0 deletions actions/get-github-actions-bot-user/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
<!-- start branding -->
<!-- end branding -->
<!-- start title -->

# GitHub Action: Get GitHub Actions Bot User

<!-- end title -->
<!-- start badges -->
<!-- end badges -->
Expand Down
3 changes: 3 additions & 0 deletions actions/get-issue-number/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
<!-- start branding -->
<!-- end branding -->
<!-- start title -->

# GitHub Action: Get Issue Number

<!-- end title -->
<!-- start badges -->
<!-- end badges -->
Expand Down
13 changes: 9 additions & 4 deletions actions/set-matrix-output/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
<!-- start branding -->
<!-- end branding -->
<!-- start title -->

# GitHub Action: Set Matrix Output

<!-- end title -->
<!-- start badges -->
<!-- end badges -->
Expand All @@ -10,7 +13,9 @@ Set matrix ouput in file to be uploaded as artifacts, because GitHub action does

<!-- end description -->

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.
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.

<!-- start contents -->
<!-- end contents -->
Expand All @@ -37,9 +42,9 @@ The GitHub Actions workflow ensures artifact uniqueness by concatenating the wor
<!-- end inputs -->
<!-- start outputs -->
| **Output** | **Description** | **Default** | **Required** |
| -------------------------- | ---------------------------------------------- | ------------------- | -------------------- |
| <code>artifact-name</code> | The real unique name of the uploaded artifact. | undefined | undefined |
| **Output** | **Description** | **Default** | **Required** |
| -------------------------- | ---------------------------------------------- | ----------- | ------------ |
| <code>artifact-name</code> | The real unique name of the uploaded artifact. | undefined | undefined |
<!-- end outputs -->
<!-- start [.github/ghadocs/examples/] -->
Expand Down
3 changes: 3 additions & 0 deletions actions/slugify/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
<!-- start branding -->
<!-- end branding -->
<!-- start title -->

# GitHub Action: Slugify

<!-- end title -->
<!-- start badges -->
<!-- end badges -->
Expand Down

0 comments on commit ddb95ba

Please sign in to comment.