parent 71dad0c

author redat97 <tarzaltreda@gmail.com> 1701207315 -0500 committer redat97 <tarzaltreda@gmail.com> 1701540145 -0500 parent 71dad0c author redat97 <tarzaltreda@gmail.com> 1701207315 -0500 committer redat97 <tarzaltreda@gmail.com> 1701539610 -0500 parent 71dad0c author redat97 <tarzaltreda@gmail.com> 1701207315 -0500 committer redat97 <tarzaltreda@gmail.com> 1701538990 -0500 issue #43: add line 80 check, config and update doc issue #45 #43: add link testing and markdown lint issue #43: config file not needed issue #43: no config file issue #43: add new config file issue #43: rename config file issue #43: test workflow issue #49: test wrap issue #43: test wrap issue #43: test wrap issue #43: test workflow issue #44: ignore pattern issue #44: change config to config-file issue #44: change pattern and move condition issue #44: update config issue #44: modify config file issue #44: update config issue #43: update config file issue #43: update config file issue #43: update config file issue #43: add config input issue #43: move inputs add ls remove show files issue #44: fix automatically issue #43: change name remove config files issue #43: run markdown on push and rm config fix trigger issue #43: add line 80 check, config and update doc issue #45 #43: add link testing and markdown lint issue #43: config file not needed issue #43: add new config file issue #43: rename config file issue #43: test workflow issue #49: test wrap issue #43: test wrap issue #43: test wrap issue #43: test workflow issue #44: ignore pattern issue #44: change config to config-file issue #44: change pattern and move condition issue #44: update config issue #44: modify config file issue #44: update config issue #43: update config file issue #43: update config file issue #43: update config file issue #43: add config input issue #43: move inputs add ls remove show files issue #43: change name remove config files issue #43: run markdown on push and rm config fix trigger
ai-cfia · Dec 2, 2023 · f07f4e6 · f07f4e6
1 parent 71dad0c
commit f07f4e6
Show file tree

Hide file tree

Showing 4 changed files with 36 additions and 19 deletions.
diff --git a/...ows/workflow-repo-standards-validation.md → .github/workflows/workflow-markdown-check.md b/...ows/workflow-repo-standards-validation.md → .github/workflows/workflow-markdown-check.md
diff --git a/.github/workflows/workflow-markdown-check.yml b/.github/workflows/workflow-markdown-check.yml
@@ -2,8 +2,12 @@ name: Check Markdown links
 
 on:
   workflow_call:
+    inputs:
+      config-file-path:
+        required: false
+        type: string
   push:
-
+    
 jobs:
   markdown-link-check:
     runs-on: ubuntu-latest
@@ -13,8 +17,11 @@ jobs:
 
     - name: Validating links
       uses: gaurav-nelson/github-action-markdown-link-check@v1
+      with:
+        config-file: '${{ inputs.config-file-path }}'
 
-    - name: Verify line 80 wrap
+    - name: Run markdown lint
       uses: DavidAnson/markdownlint-cli2-action@v14
       with:
-        config: .markdownlint.json
+        fix: true
+      if: always() # Run step even if previous steps fail.
diff --git a/.markdownlint.json b/.markdownlint.json
diff --git a/README.md b/README.md
@@ -1,28 +1,43 @@
 # AI-CFIA GitHub Workflows Repository
 
-Welcome to the GitHub Workflows repository of AI-CFIA! This repository contains various GitHub Actions workflows that assist in automating our software development processes.
+Welcome to the GitHub Workflows repository of AI-CFIA! This repository
+contains various GitHub Actions workflows that assist in automating our
+software development processes.
 
 ## Overview
 
-This repository is dedicated to providing automated solutions and workflows for various operations within our GitHub projects. It contains a collection of reusable workflows for the CI/CD pipelines, testing, and other automated processes within GitHub Actions.
+This repository is dedicated to providing automated solutions and workflows for
+various operations within our GitHub projects. It contains a collection of
+reusable workflows for the CI/CD pipelines, testing, and other automated
+processes within GitHub Actions.
 
-Each workflow has an associated documentation file that explains its purpose, usage, and any required secrets or inputs. You can find these files in the same directory as their corresponding workflow file.
+Each workflow has an associated documentation file that explains its
+purpose, usage, and any required secrets or inputs. You can find these
+files in the same directory as their corresponding workflow file.
 
 ## Workflow Documentation
 
 Here are the available workflows and their associated documentation:
 
-- [Reusable Docker Container Build](.github/workflows/workflow-build-container.md)
-- [Reusable Docker Container Deployment to Google Cloud Run](.github/workflows/workflow-deploy-gcp.md)
-- [Reusable Lint and Test Workflow for Node (React) Projects](.github/workflows/workflow-lint-test-node.md)
-- [Reusable Lint and Test Workflow for Python Projects](.github/workflows/workflow-lint-test-python.md)
-- [Reusable Workflow for Standardization Validation](.github/workflows/workflow-repo-standards-validation.md)
-- [Reusable Build and Deploy to GitHub Pages](.github/workflows/workflow-gh-pages-deployment.md)
-- [Reusable Vercel Deployment](.github/workflows/workflow-vercel-deployment.md)
+- [Reusable Docker Container
+  Build](.github/workflows/workflow-build-container.md)
+- [Reusable Docker Container Deployment to Google Cloud
+  Run](.github/workflows/workflow-deploy-gcp.md)
+- [Reusable Lint and Test Workflow for Node (React)
+  Projects](.github/workflows/workflow-lint-test-node.md)
+- [Reusable Lint and Test Workflow for Python
+  Projects](.github/workflows/workflow-lint-test-python.md)
+- [Reusable Workflow for Standardization
+  Validation](.github/workflows/workflow-markdown-check.yml)
+- [Reusable Build and Deploy to GitHub
+  Pages](.github/workflows/workflow-gh-pages-deployment.md)
+- [Reusable Vercel
+  Deployment](.github/workflows/workflow-vercel-deployment.md)
 
 ## Usage
 
-To use these workflows in your project, you can call them using `workflow_dispatch`. Here’s a basic example of how to call a workflow:
+To use these workflows in your project, you can call them using
+`workflow_dispatch`. Here’s a basic example of how to call a workflow:
 
 ```yaml
 name: <Workflow's purpose>