You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue #4045 addresses (in a kind-of artistic way) the project-leadership, with the main goal to add some policies to the contribution guide, which address the "masters of the buttons" (people who have issue-close an issue-lock rights).
Stangely, that sailbot thing locked-down the issue, whilst additionally making kind of a smart-butt comment:
Hi @lazaridis-com! It looks like you may have removed some required elements from the initial comment template, without which I can't verify that this post meets our contribution guidelines. To re-open this issue, please copy the template from here, paste it at the beginning of your initial comment, and follow the instructions in the text. Then post a new comment (e.g. "ok, fixed!") so that I know to go back and check.
Sorry to be a hassle, but following these instructions ensures that we can help you in the best way possible and keep the Sails project running smoothly.
*If you feel this message is in error, or you want to debate the merits of my existence (sniffle), please contact inquiries@sailsjs.com
Issue #4045 addresses (in a kind-of artistic way) the project-leadership, with the main goal to add some policies to the contribution guide, which address the "masters of the buttons" (people who have issue-close an issue-lock rights).
Stangely, that
sailbot
thing locked-down the issue, whilst additionally making kind of asmart-butt
comment:Please short-circuit that thing, before we witness terminator-like scenarios.
And: please open-and-unlock issue #4045, until the project lead comments / acts on this.
The text was updated successfully, but these errors were encountered: