.github: Add workflow to stale pull requests

[seemethere]

Stack from ghstack:

• .github: Add workflow to stale pull requests #51237 .github: Add workflow to stale pull requests

Stales pull requests at 150 days and then will close them at 180 days

Signed-off-by: Eli Uriegas eliuriegas@fb.com

Differential Revision: D26112086

[facebook-github-bot]

💊 CI failures summary and remediations

As of commit a56db71 (more details on the Dr. CI page):

---

• 1/5 failures introduced in this PR
• 4/5 broken upstream at merge base 6d09809 on Jan 27 from 12:00pm to 5:51pm

---

1 failure not recognized by patterns:

Job	Step	Action
pytorch_windows_vs2019_py36_cuda10.1_test1	Test	🔁 rerun

---

🚧 4 fixed upstream failures:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

If your commit is older than viable/strict, run these commands:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

Check out the recency history of this "viable master" tracking branch.

• pytorch_linux_bionic_py3_6_clang9_test on Jan 27 from 12:08pm to 5:51pm (6d09809 - 1c8d11c)
  • 🔁 rerun
• pytorch_linux_xenial_cuda10_2_cudnn7_py3_gcc7_test1 on Jan 27 from 12:08pm to 5:36pm (6d09809 - f7e90cf)
  • 🔁 rerun
• pytorch_linux_xenial_py3_clang5_asan_test1 on Jan 27 from 12:00pm to 12:49pm (dd1a97b - 16dd5ca)
  • 🔁 rerun
• pytorch_linux_bionic_py3_8_gcc9_coverage_test1 on Jan 27 from 12:00pm to 12:58pm (dd1a97b - 0b5303e)
  • 🔁 rerun

---

This comment was automatically generated by Dr. CI (expand for details).

Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions to the (internal) Dr. CI Users group.

[samestep]

As written, this seems like it will mark both PRs and issues as stale after six months, rather than only PRs; is that correct? If so, it should be changed to only act on PRs, not issues.

[yns88]

Is it better to do this as our own GitHub Action, or to use the Stale app that's already installed in this org?

[yns88]

If we add "open source" and "high priority" exemptions, then I think we can get more aggressive and close after as little as 3 months.

[seemethere]

I've added a separate job specifically for open source pull requests only

[seemethere]

As written, this seems like it will mark both PRs and issues as stale after six months, rather than only PRs; is that correct? If so, it should be changed to only act on PRs, not issues.

The usage docs from the repository indicate that if no message for issues is designated then issues will not be marked stale.

[samestep]

The usage docs from the repository indicate that if no message for issues is designated then issues will not be marked stale.

Ah thanks, I missed that!

[seemethere]

Is it better to do this as our own GitHub Action, or to use the Stale app that's already installed in this org?

I think using an action for this is better in the long run since it makes it transparent how / when it's called.

[yns88]

I think using an action for this is better in the long run since it makes it transparent how / when it's called.

Seems legit. Plus doing it this way lets us to different retentions for different sets of PRs, which doesn't seem possible with the Stale app.

[facebook-github-bot]

@seemethere merged this pull request in cc211bb.