admin: migrate to centralized linting workflows#34
Conversation
Applied via project-admin workflow Repository: ConsentInfo Operation: centralize-linting-workflows
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
There was a problem hiding this comment.
LGTM. There are no linting errors and all checks have been successful. However, this PR will conflict with #33 (the public release PR), which modifies some of the deleted local linting artifacts according to the latest Fall25 changes in Commonalities. We will resolve that if needed.
The centralized configuration in the reusable workflow is using the latest definitions from Commonalities, see https://github.com/camaraproject/tooling/tree/v0/linting/config. So you can just omit the configuration files from the release PR. |
|
@AxelNennker @sebdewet May I proceed to merge the pull request and amend pull request #33? |
CAMARA Project Admin Update - Linting Migration
This pull request migrates this repository from local linting configuration to centralized linting workflows managed by the CAMARA project.
🔄 Migration Summary
Removed local linting artifacts:
megalinter.ymlspectral_oas_lint.yml.spectral.yml.yamllint.yaml.gherkin-lintrc/lint_function/Added centralized workflows:
spectral-oas-caller.yml- Spectral linting with CAMARA rulesetpr_validation_caller.yml- Comprehensive PR validation✨ Benefits of Centralized Linting
📋 What This Means for You
🔧 Technical Details
The new workflows reference reusable workflows from:
camaraproject/tooling/.github/workflows/This ensures all repositories benefit from:
👥 Next Steps for Codeowners
Before This PR Can Be Merged:
Review linting results in PR checks:
Fix linting errors directly in this PR:
Approve and merge this PR 🚀
After Successful Merge:
Monitor the new linting system:
Test with additional rules (optional):
Monitor future PRs:
💡Pro tip: Running the Spectral workflow manually NOW is highly recommended. This allows you to fix issues proactively rather than discovering them when submitting your next feature PR!
🤖 Generated via project-admin workflow
Triggered by hdamker, executed via hdamker-bot
➡️ Next Steps: This PR should be reviewed, fixed as needed, approved, and merged by repository codeowners following standard review processes.
This is a manually triggered automated administrative update.