create a locked issue for announcements #7520
-
I’m using Shields for my public projects on GitHub, and I’d like to be notified when there is something deprecated (thus potential breaking change ahead). How about creating a locked issue (so that it won’t be spammed), then post news about breaking changes there? After that we can mention such a “mailing list” in ReadMe, so users can subscribe to it. An example in the past is #5773. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
This is something we've mentioned before #7017 and broadly agree. Just to clarify: You say
but then the issue you've linked to is a breaking change for self-hosting users. Are you interested in hearing about changes affecting users of shields.io or changes affecting users who host their own instance? |
Beta Was this translation helpful? Give feedback.
This is something we've mentioned before #7017 and broadly agree.
Just to clarify: You say
but then the issue you've linked to is a breaking change for self-hosting users. Are you interested in hearing about changes affecting users of shields.io or changes affecting users who host their own instance?