-
-
Notifications
You must be signed in to change notification settings - Fork 279
new plugin system #495
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
Labels
issue-status: wait-for-implementation
maintainers agree on the bug / feature
type: feature
A new enhacement proposal
Comments
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 5, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
4 tasks
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 6, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 6, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 13, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 13, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 13, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 13, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 13, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 13, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 13, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 13, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 13, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 21, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
noirbizarre
added a commit
to noirbizarre/commitizen
that referenced
this issue
Dec 24, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes commitizen-tools#495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
Lee-W
pushed a commit
that referenced
this issue
Dec 29, 2022
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes #495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
Lee-W
pushed a commit
that referenced
this issue
Jan 21, 2023
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes #495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
Lee-W
pushed a commit
that referenced
this issue
Jan 23, 2023
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes #495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
Lee-W
pushed a commit
that referenced
this issue
Jan 25, 2023
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes #495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
Lee-W
pushed a commit
that referenced
this issue
Feb 11, 2023
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes #495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
Lee-W
pushed a commit
that referenced
this issue
Mar 2, 2023
…n loading Plugins are now loaded using the `commitizen.plugin` entrypoint while legacy plugin are not loaded anymore but a warning is raised when one is seen. Fixes #495 BREAKING CHANGE: Plugins are now exposed as `commitizen.plugin` entrypoints
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
issue-status: wait-for-implementation
maintainers agree on the bug / feature
type: feature
A new enhacement proposal
Description
As discussed on on issue 287, we could try Python Entry Points Explained or poetry - plugins to implement a new plugin system so that package with
cz_
prefix but not commitzen plugins won't be loaded. (this issue was solved on PR #480 , but refactoring the plugin system might make it easier to maintain in the future)Possible Solution
No response
Additional context
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: