The problem

When the issue is marked as stale AND the author responds, the issue will continue to be marked as stale and MSBuild wants to avoid this scenario. See this example in this repo

The solution

Add some sort of add-labels-when-updated-from-stale and remove-labels-when-updated-from-stale to allow this automation:

1. Github action checks only X label for stale-ness
2. After 30 days of inactivity, mark issues with X label as stale
3. Customer responds
4. Action should remove stale label AND remove X label so prevent action from marking as stale again. It could also add some sort of "needs team response" label.