Currently users need to have a clone of opam-repository locally available to create a new branch, add the generated opam files, commit, push and open a PR to opam-repository to get it merged.
The GitHub GraphQL API offers createCommitOnBranch and createPullRequest which should allow creating a PR without having to clone opam-repository. Paired with #409 this would mean that the user doesn't necessarily need to do anything in addition to have their changes included in opam-repository.
Of course, existing usecases with people with existing clones should remain supported, since that's also a common usecase, especially if changes are requested by OPAM Repository maintainers.
Currently users need to have a clone of
opam-repositorylocally available to create a new branch, add the generatedopamfiles, commit, push and open a PR toopam-repositoryto get it merged.The GitHub GraphQL API offers
createCommitOnBranchandcreatePullRequestwhich should allow creating a PR without having to cloneopam-repository. Paired with #409 this would mean that the user doesn't necessarily need to do anything in addition to have their changes included inopam-repository.Of course, existing usecases with people with existing clones should remain supported, since that's also a common usecase, especially if changes are requested by OPAM Repository maintainers.