Closed ryjones closed 5 years ago
I wonder if the PR branches also need the stale.yml or is it enough to have it in master
@rizbe I tested this, and it appears having it in master is enough. You'll note one of my prs is on master, where it is merged, and one on another branch, where it isn't yet merged. Neither fired.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
Still an issue
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
@ryjones you are missing the 'stale' label on that repository (which is the label you have configured in the stale.yml file).
I am assuming that would be why you aren't seeing any change.
The stale bot is not firing as expected. I have it installed and enabled on all repos for the organization that I own: https://github.com/organizations/hyperledger/settings/installations
I added the following stale.yml, after testing it on my personal repos, to a repo here: https://github.com/hyperledger/fabric/blob/master/.github/stale.yml
This PR is on 1.4, which does not have stale.yml: https://github.com/hyperledger/fabric/pull/209
This PR is on master, which does: https://github.com/hyperledger/fabric/pull/208
Why is it not firing?
It is firing for some projects in the Hyperledger org, but it is not firing for fabric (and maybe more repos, but I haven't checked every repo)