Skip to content
This repository has been archived by the owner on May 20, 2023. It is now read-only.

README.md - Rewording and spacing corrections #272

Merged
merged 2 commits into from
Apr 24, 2020
Merged

README.md - Rewording and spacing corrections #272

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
97ba9cc
Rewording and spacing corrections
jwhett Mar 23, 2020
c5a9a09
Update README.md
JamesMGreene Apr 24, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ limitPerRun: 30

## How are issues and pull requests considered stale?

The app uses GitHub's [updated](https://help.github.com/articles/searching-issues/#search-based-on-when-an-issue-or-pull-request-was-created-or-last-updated) search qualifier to determine staleness. Any change to an issues and pull request is considered an update, including comments, changing labels, applying or removing milestones, or pushing commits.
The app uses GitHub's [updated](https://help.github.com/articles/searching-issues/#search-based-on-when-an-issue-or-pull-request-was-created-or-last-updated) search qualifier to determine staleness. Any change to an issue or pull request is considered an update, including comments, changing labels, applying or removing milestones, or pushing commits.

An easy way to check and see which issues or pull requests will initially be marked as stale is to add the `updated` search qualifier to either the issue or pull request page filter for your repository: `updated:<2017-07-01`. Adjust the date to be 60 days ago (or whatever you set for `daysUntilStale`) to see which issues or pull requests will be marked.

Expand Down