docs(submitting): add how to use pkg review tool - #152
Conversation
...Package developers can review their own packages before they get to the stage of being a PR. This somewhat replaces the now-outdated presence of Step 7 in the old Package submission guidance which advised installing `ChannelRepositoryTools` Package and run its command and ensure they passed before submitting Packages.
vwheeler63
changed the title
|
Also available as a GitHub Action for reviewing a single package. |
Hi, Michael! ( @michaelblyons ) I saw in the code how it is geared towards running in an environment like package_control_channel where it looks at the diffs of the "repository.json" files (e.g. m.json) and traces down the originating repository, clones that remote repository, and then reviews it in its "runner" space. Are you aware whether it can be used as a GitHub Action in, for example, my own Package repository? I looked around at a few high-end Package repositories (e.g. PackageControl, PackageDev and LSP) and didn't see it set up to run there as a GitHub Action. Are you aware of any examples? Kind regards, |
It can do both.
I added an example to GitLink this week. For the moment, I have mine set only to run manually, but you could ask it to check PRs or whatever. |
Very slick!! Thank you! |
2 participants
Fixes: #151
This addresses the omission spelled out in #151, enabling package developers to do a better review of their own work before submitting new packages as PRs.