Configuring Stale with Github Labels with Emoji

[bmuenzenmeyer]

Could you provide an example of how to configure stale.yml with Github's new emoji in labels?

exemptLabels:
  - pinned ⚓️

or

exemptLabels:
  - pinned :anchor:

Thanks!!!

[LeoNatan]

It's already supported as can be seen here:
https://github.com/wix/detox/blob/master/.github/stale.yml

Use "" when using an emoji.

GitHub

wix/detox

detox - Gray Box E2E Tests and Automation Library for Mobile Apps

[bmuenzenmeyer]

Thanks!

[snipe]

Sorry to resurrect this one, but I'm having an issue ever since we added emoji to the labels. Issues that shouldn't ever be closed (exempt) are still being marked as stale and/or closed.

My stale.yml:

# Number of days of inactivity before an issue becomes stale
daysUntilStale: 60
# Number of days of inactivity before a stale issue is closed
daysUntilClose: 7
# Issues with these labels will never be considered stale
exemptLabels:
  - pinned
  - security
  - :woman_technologist: ready for dev
  - :moneybag: bounty
  - :hand: bug
  - "🔐 security"
  - "👩‍💻 ready for dev"
  - "💰 bounty"
  - "✋ bug"

exemptMilestones: true

# Label to use when marking an issue as stale
staleLabel: stale

only: issues

# Comment to post when removing the stale label.
unmarkComment: >
  Okay, it looks like this issue or feature request might still be important. We'll re-open
  it for now. Thank you for letting us know!

# Comment to post when marking an issue as stale. Set to `false` to disable
markComment: >
  Is this still relevant? We haven't heard from anyone in a bit. If so,
  please comment with any updates or additional detail.

  This issue has been automatically marked as stale because it has not had
  recent activity. It will be closed if no further activity occurs. Don't
  take it personally, we just need to keep a handle on things. Thank you
  for your contributions!
# Comment to post when closing a stale issue. Set to `false` to disable
closeComment: >
  This issue has been automatically closed because it has not had
  recent activity. If you believe this is still an issue, please confirm that
  this issue is still happening in the most recent version of Snipe-IT and reply
  to this thread to re-open it.

You can see an example of a issues affected by this here:
snipe/snipe-it#3286
snipe/snipe-it#5881

Am I missing something obvious? (It's entirely possible that I am)

Thanks in advance, and thanks for such a useful bot!