Repository navigation
Copilot/update bcquality workflow execution - #252
Theo van de Ven (rs-tve) wants to merge 19 commits into
Conversation
Co-authored-by: rs-tve <110678314+rs-tve@users.noreply.github.com>
…orkflow [WIP] Implement reusable workflow scaffold for customer PR review
Added error handling for missing bcquality-findings.json file in Copilot step.
Updated tool permissions in review-customer-pr.yml to allow specific shell commands.
Added condition to check for hard incomplete status in review execution.
…rkflow Co-authored-by: rs-tve <110678314+rs-tve@users.noreply.github.com>
|
Thank you for contributing, Theo van de Ven (@rs-tve). This PR was closed automatically because it changes custom-layer content. Keep company-only rules in your fork and point your host at that copy. The If the guidance is useful to everyone, submit it to the layer that owns the Files in this PR that triggered the auto-close
Template changes to |
|
👋 Heads up Theo van de Ven (@rs-tve) — and cc maintainers — this PR introduces new top-level entries that aren't part of BCQuality's known repository structure:
This isn't a block — just a flag. 🚩 New top-level folders and files are usually unintended (a stray export, a tool's scratch dir, or content that meant to land inside an existing layer). BCQuality keeps a deliberately small root: plugin metadata, If this was intentional and the new entry genuinely belongs at the repo root, a maintainer can review and merge as normal — no action needed beyond a quick sanity check. If it wasn't, please move the content into the right existing layer (or drop it) and push an update. 🙏 A maintainer will take a look before merging. |
|
Theo van de Ven (@rs-tve) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
No description provided.