-
Notifications
You must be signed in to change notification settings - Fork 37
[bug] No autogenerated message displayed for new Issue #33
Comments
I was assuming that the "bot-message" is displayed for every new issues but recently learned that is only for new users. It would be nice to have the bot-message for every new issue, at least for a period of time until we streamline the process. Bot message - Since this is your first issue, we kindly remind you to check out EIP-1 for guidance. If this issue was created as a “discussions-to” for an EIP or to discuss an idea for an EIP, please close it and create a thread at Fellowship of Ethereum Magicians. |
If we switch to having the bot comment on every new issue then we should remove the bit at the start that says "Since this is your first issue, ".
|
@MicahZoltu @poojaranjan what do you all feel is the best next step here? |
I think we decided in the meeting that the bot should comment on every issue. If it does, I still recommend the text in my previous comment. Does anyone remember if this was decided or not? @poojaranjan @lightclient? |
Okay, I'll add it. It will be easy to change if it's not desirable |
I am fine with suggested changes by @MicahZoltu. I think it make sense to remove the first issue statement. |
I have to revisit the decision, but I suppose adding the comment to every new issue created, will help users to read and follow. |
Yes, the bot-comment should be added to every issue, be it from a The eip-1, itself, can go under updates that both might not be aware of.
Also, should we provide the link to Fellowship of Ethereum Magicians? |
Yes, the Ethereum magicians reference should be a link. |
This was implemented via ethereum/EIPs@4031ae6 |
Based on earlier addition to bot's functionality, the general expectation is that for a new Issue, bot should display a message for the user to ensure the issue created is not for the "discussion-to".
Unfortunately, I don't see any such message for the Issue 4500
Someone might want to look into it.
The text was updated successfully, but these errors were encountered: