Adding the stale.yml based on react-native core and react-native-share

[MateusAndrade]

Summary

As discussed on https://github.com/react-native-community/react-native-share/pull/503. I added a simple stale.yml using pro-bot stale to handle old issues on react-native-share. With @jgcmarins help, the pro-bot have been configured beign able to handle old issues without any problem.

Motivation

Since there is a lot of issues open on react-native-share, i decided with @jgcmarins to add a simple stale bot to handle old issues By doing this, we got a reply from some issues, that dont have been given the properly attention.

My suggestion is: would be interesting having a default stale.yml to be applied on the repos under react-native-community umbrella. We just need to ensure that these repos got some default labels like:

• pinned
• security
• pinned
• discussion

By doing this, we can close old issues easily and see if there is been a reply from the author without having to read every issue on the repo.

Also, i think that setting some bots apart from the stale would be super productive, we can even use react-native as a base for this. :smile:

Bwt, i hope this helps in further discussions. =D

[kelset]

I spent a bit of time thinking about the labels, and compared it with the standard set of labels that a default github repo as (example: https://github.com/kelset/test-react-nav-with-screens/labels) but tbh I think that we can proceed with the 3 labels that you have identified for now.

[MateusAndrade]

I spent a bit of time thinking about the labels, and compared it with the standard set of labels that a default github repo as (example: https://github.com/kelset/test-react-nav-with-screens/labels) but tbh I think that we can proceed with the 3 labels that you have identified for now.

I think opening a discussion about this a good way to go. What do you think?