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

No check for bad dev repo name #133

Open
rlepigre opened this issue Feb 28, 2022 · 1 comment
Open

No check for bad dev repo name #133

rlepigre opened this issue Feb 28, 2022 · 1 comment

Comments

@rlepigre
Copy link

Not sure if this is intended or not, but when publishing bindlib.6.0.0 it was noticed that I had made a mistake in the name of the github repo for the project in the bindlib.opam file generated by dune (here is the commit fixing the problem). It seems like something opam-publish could have easily caught, since it knows the actual URL of the repo.

@rjbou
Copy link
Contributor

rjbou commented Nov 8, 2022

It can be added to linting, another candidate to linting opam repo plugin @kit-ty-kate

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

No branches or pull requests

2 participants