Package eugener_test_ocaml.0.1.0

[eugenebmx]

eugener_test_ocaml.0.1.0

A short synopsis
A longer description

---

• Homepage: https://github.com/username/reponame
• Source repo: git+https://github.com/username/reponame.git
• Bug tracker: https://github.com/username/reponame/issues

---

🐫 Pull-request generated by opam-publish v2.4.0

[shonfeder]

This appears to be PR spam, as none to the content in the changest or the PR is meaningful. I will move to have this account banned from opening PRs in the repo.

[mtelvers]

This looks more like someone who is learning how to publish a package on opam-repository. While we wouldn't want to publish an empty project I think moving to have the account blocked is a bit draconian. We want to encourage contributors to opam-repository and promote OCaml not put them off for life.

[shonfeder]

@mtelvers have you looked at the account? https://github.com/eugenebmx

I of course want to be welcoming to new comers. If @eugenebmx chimes in to show signs of being a human trying to figure out how to publish, then I will offer profuse apologies.

[shonfeder]

See also #26942

[eugenebmx]

@mtelvers have you looked at the account? https://github.com/eugenebmx

I of course want to be welcoming to new comers. If @eugenebmx chimes in to show signs of being a human trying to figure out how to publish, then I will offer profuse apologies.

Hey @shonfeder and @mtelvers !
Sorry for creating a lot of noise. Copilot is not really helpful in creating correct .opam files, thus, I keep getting more small errors that break the build.
I'm conducting security research on all major package repos, and as a part of it, I upload a test package to see how the package repo behaves in certain situations.
If you need any proof of me being a human, I'd gladly provide it. And, of course, as soon as the research is done, I'll do the clean up.

[shonfeder]

Thank you for clarifying, @eugenebmx. I apologize for assuming your account was a bot account (for context, we have seen a few of these creating spam on GitHub recently). I should not have jumped to conclusions.

Regarding use of usual use of this repository, as a rule we expect that PRs into this repo will be in furtherance of a package which the author intends to publish, or of some maintenance or support work of the repository itself. This repository is high traffic and high-touch, and it is not in general a suitable target for testing tooling or conducting research that requires opening PRs that are not actually meant to publish packages. We may be able to make exceptions for certain kinds of tests or research activities, but we will need to evaluate that kind of usage on a case-by-case basis.

All that said, if you need support learning how to write and publish opam packages, we would be happy to provide guidance. In addition to consulting https://opam.ocaml.org/doc/Packaging.html, asking questions on discuss.ocaml.org is a good place to start. Once you have a working package, we are always happy to help first time publishers here.

On the other hand, if you are trying to test an automated publication tool or trying to experiment with publication on opam package repositories, you can work off your own fork of the package repo. Since you are using opam publish you can look at using the --repo flag to target your experimental publications at your own fork.

Finally, if you think that your research would add value to the OCaml community and think it warrants an exception, I invite you to open an issue describing what you are working on to seek an exception to our usual guidelines. You can see more details about the policies for our repository at https://github.com/ocaml/opam-repository/wiki/Policies .

Please let me know if you have any questions and, again, I apologize for my incorrect assumption and the resulting harsh response.