Closed BenjaminVanRyseghem closed 6 years ago
What about simply a publish
option? Then if it's explicitly set to true
, we do not turn off the publish capability.
and what if it's set to false
? I mean, for copyrighted we keep the same behavior, but should we extend this behavior to the other licenses then?
Yeah, we'd need to respect receiving a false
value.
Sorry for leaving this PR hanging for so long. I hadn't realized new code had been pushed. Thanks for sending this out!
no problemo :smile:
Add the ability to not set the package private when the code is copyrighted.
My use case is when the code is copyrighted, but also published in a company-only repository. In this case, it's safe to
publish
the package.