-
Notifications
You must be signed in to change notification settings - Fork 13
Docs: explain how to block packages #128
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! I added 2 suggestions, but you decide if they make sense :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work
Co-authored-by: Igor Benko <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@@ -190,9 +190,9 @@ Once a custom package has been added to Private Packagist you will benefit from | |||
|
|||
### Prevent a package from being used with custom packages | |||
|
|||
While there is no direct "block package" feature in Packagist, you can effectively prevent a specific package from being used by creating a placeholder package. | |||
While there is no direct "block package" feature in Packagist, you can effectively prevent a specific package from being used in your project by creating a placeholder package. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of saying project we could generalize it and say Composer repository? Or (sub-)organization?
Project (for me) is really just a package with a composer.json + .lock file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest "your Composer project" then? It's about blocking usage in your codebase, not in the Private Packagist org/repository?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
slightly different
Co-authored-by: Igor Benko <[email protected]>
Add an example on how to use custom packages to block a package.