Skip to content
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

Investigate using eipw to check PIPs in pull requests #117

Open
SamWilsn opened this issue Sep 21, 2023 · 1 comment · May be fixed by #158
Open

Investigate using eipw to check PIPs in pull requests #117

SamWilsn opened this issue Sep 21, 2023 · 1 comment · May be fixed by #158

Comments

@SamWilsn
Copy link

Hey!

I'm the author of eipw, the tool we use to check EIPs for consistency in pull requests. eipw is a markdown lint tool, and is not the bot that handles merging and permissions for EIPs.

If you folks are interested, we could investigate whether eipw would be a useful tool to integrate with this repository. Personally, I'd love to see it get adopted by other projects, and maybe even increase the bus factor above one.

If you aren't familiar with eipw, it's the tool that generates these annotations:

image

It can be configured using TOML, like so:

[lints.markdown-re-pip-dash]
kind = "markdown-regex"
mode = "excludes"
pattern = '(?i)pip[\s]*[0-9]+'
message = "proposals must be referenced with the form `PIP-N` (not `PIPN` or `PIP N`)"
@SamWilsn SamWilsn linked a pull request Oct 18, 2023 that will close this issue
@noelportillo
Copy link

Goog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants