chore: Disable issue/PR chasing scheduled-search automations#2798
Merged
Conversation
…age documentation
Comment out scheduled searches that comment on or chase module owners/issue authors, keeping label-only automations. Update issue triage automation docs with disabled notices and applicability tables.
microsoft-github-policy-service
Bot
added
the
Needs: Triage 🔍
|
Important The "Needs: Triage 🔍" label must be removed once the triage process is complete! Tip For additional guidance on how to triage this issue/PR, see the AVM Issue Triage documentation. |
This was referenced Jul 10, 2026
Merged
ITA06 now only applies the 'Needs: Triage' label and no longer comments on every new issue/PR. Add a top-level note that these automations are temporarily disabled/reduced to avoid notification fatigue and will be refined and re-enabled in the near future.
jtracey93
changed the title
jaredfholgate
approved these changes
Jul 13, 2026
jtracey93
added a commit
to Azure/bicep-registry-modules
that referenced
this pull request
Jul 13, 2026
## Summary As agreed by the AVM team, this disables / reduces the GitHub Policy Service automations that **comment on or chase** module owners / issue authors, to cut notification fatigue. Label-only and other non-harassing automations remain enabled. ## Changes - `.github/policies/scheduledSearches.yml` — commented out the chasing scheduled searches: - **ITA01BCP.1 / ITA01BCP.2** — "response overdue" triage chase (mention + label) - **ITA02BCP.1 / ITA02BCP.2** — "needs immediate attention" chase (mention + label) - **ITA03BCP** — security bug overdue chase (comment + label) - **ITA04** — stale `Needs: Author Feedback` reminder comment - `.github/policies/eventResponder.yml` — **ITA06** now only applies the `Needs: Triage` label; the comment (reply) it used to post on **every** new issue/PR has been **removed**. The remaining `eventResponder.yml` rules (label add/remove and friendly acknowledgements) stay in place. ## Related PRs Part of a coordinated change across the AVM repositories: - AVM Core (parent, incl. docs updates): Azure/Azure-Verified-Modules#2798 - TF governance: Azure/avm-terraform-governance#519 > [!NOTE] > The documentation for these rules is updated in the AVM Core PR above. ## Related issue Related to https://msft.ghe.com/azure-cloud-native/Azure-Verified-Modules/issues/164
jtracey93
added a commit
to Azure/avm-terraform-governance
that referenced
this pull request
Jul 13, 2026
## Summary As agreed by the AVM team, this disables / reduces the GitHub Policy Service automations that **comment on or chase** module owners / issue authors, to cut notification fatigue. Label-only and other non-harassing automations remain enabled. ## Changes - `managed-files/root/.github/policies/scheduledSearches.yml` — commented out the chasing scheduled searches: - **ITA01TF.1 / ITA01TF.2** — "response overdue" triage chase (mention + label + assign) - **ITA02TF.1 / ITA02TF.2** — "needs immediate attention" chase (mention + label) - **ITA03TF** — security bug chase (mention + label + assign) - **ITA04** — stale `Needs: Author Feedback` reminder comment - `managed-files/root/.github/policies/eventResponder.yml` — **ITA06** now only applies the `Needs: Triage` label; the comment (reply) it used to post on **every** new issue/PR has been **removed**. These managed files are synced out to all TF module repositories on a schedule, so these changes propagate to every Terraform module repo. The remaining `eventResponder.yml` rules (label add/remove and friendly acknowledgements) stay in place. ## Related PRs Part of a coordinated change across the AVM repositories: - AVM Core (parent, incl. docs updates): Azure/Azure-Verified-Modules#2798 - BRM: Azure/bicep-registry-modules#7204 > [!NOTE] > The documentation for these rules is updated in the AVM Core PR above. ## Related issue Related to https://msft.ghe.com/azure-cloud-native/Azure-Verified-Modules/issues/164
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
As agreed by the AVM team, this disables / reduces the GitHub Policy Service automations that comment on or chase module owners / issue authors, to cut notification fatigue. Label-only and other non-harassing automations remain enabled.
This PR also includes a couple of small, pre-existing documentation updates that were already on this branch (see below).
Changes
Automation changes
.github/policies/scheduledSearches.yml— commented out the chasing scheduled searches:Needs: Author Feedbackreminder comment.github/policies/eventResponder.yml— ITA06 now only applies theNeeds: Triagelabel; the comment (reply) it used to post on every new issue/PR has been removed.docs/content/help-support/issue-triage/issue-triage-automation.md— added "currently disabled" notices to each disabled rule (ITA01BCP, ITA02BCP, ITA03BCP, ITA01TF, ITA02TF, ITA03TF, ITA04, ITA24), documented the ITA06 comment removal, added a top-level note explaining these automations are temporarily disabled/reduced to avoid notification fatigue and will be refined and re-enabled in the near future, bracketed the disabled cells in the schedule-based applicability table, and corrected the ITA05 applicability (disabled in AVM Core and BRM; not present in the Terraform repositories).The remaining
eventResponder.ymlrules (label add/remove and friendly one-shot acknowledgements) stay in place.Other documentation updates already on this branch
docs/content/help-support/issue-triage/avm-issue-triage.md— updated the internal "Module Index update process" link from the olddev.azure.comwiki URL to the currenteng.msdocs URL.docs/content/help-support/issue-triage/avm-organizer-bot.md— renamed "AVM Organizer Bot" / "AVM Team Linter" to "Azure Verified Modules GitHub App" and updated the GitHub App link fromapps/avm-team-lintertoapps/azure-verified-modules.Companion PRs
These apply the same automation changes in the other AVM repositories:
Related issue
Related to https://msft.ghe.com/azure-cloud-native/Azure-Verified-Modules/issues/164