-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@eth-bot gives EIP file name error problem for new submission #4398
Comments
Very descriptive. Thank you! |
@poojaranjan @julesl23 this is intended behavior. all eip's should be assigned eip numbers before they are merged initially. Can I close this? |
When the PR is originally opened it will not have an EIP number. An editor will assign an EIP number after the PR is created. The current behavior results in an error for every correctly constructed new EIP, which is mildly annoying. Can we look for the recommended filename of
|
Sure @MicahZoltu I'll add this feature |
okay so as an update this implements the requested feature. In particular it checks that
|
because I believe this meets all requirements I wlll close this issue. I will follow up on this if more problems arise. |
@poojaranjan this is intended behavior when a file is not named correctly. What behavior would you prefer? Also please open a issue in eth-bot 😊
Originally posted by @alita-moore in #4393 (comment)
The pull request link #4393 with the problem
@eth-bot
The documentation from https://github.com/ethereum/EIPs/blob/master/eip-template.md
specifies "When opening a pull request to submit your EIP, please use an abbreviated title in the filename, eip-draft_title_abbrev.md."
When I do that, eth-bot returns with error "Error: EIP file name must be eip-###.md"
I don't know which is correct. But neither didn't seem to work with me and gives
Auto-Merge Bot / EIP Auto-Merge Bot (pull_request_target) Failing after 27s — EIP Auto-Merge Details
Clicking details highlights the line
Error: EIP file name must be eip-###.md
The text was updated successfully, but these errors were encountered: