Add operations-per-run limit to stale issues workflow #6289
Conversation
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
Currently we are running everyday at 3am, it will grab 30 at a time (it does auto paginate), picks up where it left off. However, at this pace will take ~31 days to get through our issues. However when new issues are added, it starts over.
spboyer
requested review from
danieljurek,
rajeshkamal5050,
tg-msft and
vhvb1989
as code owners
JeffreyCA
approved these changes
Nov 26, 2025
kristenwomack
approved these changes
Dec 3, 2025
Collaborator
|
@rajeshkamal5050 - will you review and push this change? Looks like it needs one code owner. |
rajeshkamal5050
approved these changes
Dec 3, 2025
vhvb1989
approved these changes
Dec 4, 2025
Member
|
/check-enforcer override |
JeffreyCA
pushed a commit
to JeffreyCA/azure-dev
that referenced
this pull request
Dec 5, 2025
Currently we are running everyday at 3am, it will grab 30 at a time (it does auto paginate), picks up where it left off. However, at this pace will take ~31 days to get through our issues. However when new issues are added, it starts over.
JeffreyCA
pushed a commit
to JeffreyCA/azure-dev
that referenced
this pull request
Dec 5, 2025
Currently we are running everyday at 3am, it will grab 30 at a time (it does auto paginate), picks up where it left off. However, at this pace will take ~31 days to get through our issues. However when new issues are added, it starts over.
JeffreyCA
pushed a commit
to JeffreyCA/azure-dev
that referenced
this pull request
Dec 8, 2025
Currently we are running everyday at 3am, it will grab 30 at a time (it does auto paginate), picks up where it left off. However, at this pace will take ~31 days to get through our issues. However when new issues are added, it starts over.
JeffreyCA
pushed a commit
to JeffreyCA/azure-dev
that referenced
this pull request
Dec 8, 2025
Currently we are running everyday at 3am, it will grab 30 at a time (it does auto paginate), picks up where it left off. However, at this pace will take ~31 days to get through our issues. However when new issues are added, it starts over.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently we are running everyday at 3am, it will grab 30 at a time (it does auto paginate), picks up where it left off. However, at this pace will take ~31 days to get through our issues. However when new issues are added, it starts over.