Skip to content

chore(gha): update yamllint.yml GitHub workflow - #138

Merged
jvdadda merged 1 commit into
masterfrom
mobsuccessbot/workflow-yamllint
Aug 13, 2026
Merged

chore(gha): update yamllint.yml GitHub workflow#138
jvdadda merged 1 commit into
masterfrom
mobsuccessbot/workflow-yamllint

Conversation

@ms-bot

@ms-bot ms-bot commented Aug 12, 2025

Copy link
Copy Markdown
Contributor

Why is this needed?

This pull request has been created by a robot to update the yamllint.yml GitHub workflow.

@ms-bot ms-bot added the mobsuccessbot Pull requests that enforce company policies label Aug 12, 2025
@jvdadda
jvdadda marked this pull request as draft October 14, 2025 09:46
@ms-bot
ms-bot force-pushed the mobsuccessbot/workflow-yamllint branch 2 times, most recently from 79df586 to d4ba6ca Compare November 14, 2025 10:43
@ms-bot
ms-bot force-pushed the mobsuccessbot/workflow-yamllint branch from d4ba6ca to a316168 Compare November 24, 2025 10:42
@ms-bot
ms-bot force-pushed the mobsuccessbot/workflow-yamllint branch from a316168 to d33bed8 Compare January 8, 2026 12:41
@ms-bot
ms-bot force-pushed the mobsuccessbot/workflow-yamllint branch 4 times, most recently from b85bef9 to ff4f6ae Compare January 27, 2026 10:41
@ms-bot
ms-bot force-pushed the mobsuccessbot/workflow-yamllint branch from ff4f6ae to ea131f6 Compare March 9, 2026 09:43
@ms-bot
ms-bot force-pushed the mobsuccessbot/workflow-yamllint branch 2 times, most recently from 62d058b to b167976 Compare July 3, 2026 13:49
@ms-bot
ms-bot force-pushed the mobsuccessbot/workflow-yamllint branch 3 times, most recently from 7aa4f70 to 62670e4 Compare July 28, 2026 10:41
@ms-bot
ms-bot force-pushed the mobsuccessbot/workflow-yamllint branch from 62670e4 to 8970a56 Compare July 30, 2026 13:52
@maximus-agents

maximus-agents Bot commented Aug 4, 2026

Copy link
Copy Markdown

🤖 fix-approve-merge

Outcome: PROCESSING 🔄

Maximus detected this workflow pull request and is checking CI, Linear, review comments, and merge eligibility.

@ms-bot
ms-bot force-pushed the mobsuccessbot/workflow-yamllint branch 3 times, most recently from 4261426 to 4e80da1 Compare August 10, 2026 12:42
@ms-bot
ms-bot force-pushed the mobsuccessbot/workflow-yamllint branch 2 times, most recently from 0974869 to fcc4157 Compare August 11, 2026 16:54
@ms-bot
ms-bot force-pushed the mobsuccessbot/workflow-yamllint branch from fcc4157 to 543760c Compare August 13, 2026 08:46
@jvdadda
jvdadda marked this pull request as ready for review August 13, 2026 13:47
Copilot AI lite review requested due to automatic review settings August 13, 2026 13:47

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the repository’s yamllint.yml GitHub Actions workflow, shifting the job runner to ubuntu-slim and adding an explicit yamllint installation step so YAML linting can still run in that environment.

Changes:

  • Switch runs-on from ubuntu-latest / ubuntu-24.04 to ubuntu-slim for the YAML validation and notify jobs.
  • Update the checkout action version and add a step to install a pinned yamllint version before running the lint command.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread .github/workflows/yamllint.yml

@jvdadda jvdadda left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approuvé automatiquement : PR de synchronisation de workflow générée par ms-bot, tous les checks requis sont verts.

@jvdadda
jvdadda merged commit 2db17fb into master Aug 13, 2026
9 checks passed
@jvdadda
jvdadda deleted the mobsuccessbot/workflow-yamllint branch August 13, 2026 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mobsuccessbot Pull requests that enforce company policies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants