[FabricBot] Remove usage of 'noActivitySince' operand condition - #53256
Merged
wtgodbe merged 2 commits intoJan 10, 2024
Merged
Conversation
ghost
added
the
area-infrastructure
|
Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at. |
wtgodbe
approved these changes
Jan 10, 2024
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.
[FabricBot] Remove usage of 'noActivitySince' operand condition
This removes the event responder task for automatically replying to semi-stale issue comments.
Description
With the pending migration away from FabricBot to the Policy Service bot, the
noActivitySinceevent condition will no longer be supported. This PR removes the only occurrence of that condition in this repository's configuration. The condition was used to identify comments left on issues that have not had prior activity for 7 days, suggesting that a new issue be filed instead. This task had never been triggered within this repository.This PR also corrects the name of the Locker workflow. PR #53225 updated the workflow to only apply to issues, but the name of the workflow was not updated.
Note: The
noActivitySincesearch condition will still be supported within scheduled searches as used in this configuration; it's only unsupported in event triggers going forward.