Add .github/stale.yml for stale bot in case we add it #1125
No reviewers
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1125
Loading…
Reference in New Issue
No description provided.
Delete Branch "stale"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I first suggested it in https://github.com/privacytoolsIO/privacytools.io/issues/977#issuecomment-502433728 and talked about it in Wire where @blacklight447-ptio supports the idea.
I checked the install page and made a request I think will come to @BurungHantu1605 and @JonahAragon and in case you approve it, this file should be created with rules on how it works.
Deploy preview for privacytools-io ready!
Built with commit
275bf0c14c
https://deploy-preview-1125--privacytools-io.netlify.com
Good idea!
@JonahAragon @BurungHantu1605 This PR has been open for a bit over three months. I would like to request the bot to be added again as I am having a feeling of drowning under the flood of new issues.
CC: @privacytoolsIO/editorial
@JonahAragon @BurungHantu1605 I could theoretically merge this, but I would prefer you adding the bot first.