Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
P
python-poetry
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
open
python-poetry
Commits
d508c9f0
Unverified
Commit
d508c9f0
authored
Jul 03, 2023
by
Micael Jarniac
Committed by
GitHub
Jul 04, 2023
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
docs(pre-commit): fix FAQ grammar (#8150)
parent
5b0cb4be
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
7 deletions
+7
-7
docs/pre-commit-hooks.md
+7
-7
No files found.
docs/pre-commit-hooks.md
View file @
d508c9f0
...
@@ -109,16 +109,16 @@ repos:
...
@@ -109,16 +109,16 @@ repos:
`pre-commit autoupdate`
updates the
`rev`
for each repository defined in your
`.pre-commit-config.yaml`
`pre-commit autoupdate`
updates the
`rev`
for each repository defined in your
`.pre-commit-config.yaml`
to the latest available tag in the default branch.
to the latest available tag in the default branch.
Poetry follows a branching strategy
, where the default branch is the active development branch
Poetry follows a branching strategy
where the default branch is the active development branch,
and fixes get
s back
ported to stable branches. New tags are assigned in these stable branches.
and fixes get
back
ported to stable branches. New tags are assigned in these stable branches.
`pre-commit`
does not support such a branching strategy and has decided to not implement
`pre-commit`
does not support such a branching strategy and has decided to not implement
an option, either on the
[
user side
](
https://github.com/pre-commit/pre-commit/issues/2512
)
an option, either on the
[
user
's
side
](
https://github.com/pre-commit/pre-commit/issues/2512
)
or
[
hook author side
](
https://github.com/pre-commit/pre-commit/issues/2508
)
, to define a branch for lookup the latest
or
the
[
hook author's side
](
https://github.com/pre-commit/pre-commit/issues/2508
)
, to define a branch for looking
available tag.
up the latest
available tag.
Thus,
`pre-commit autoupdate`
is not usable for the hooks described here.
Thus,
`pre-commit autoupdate`
is not usable for the hooks described here.
You can avoid changing the
`rev`
to an unexpected value
,
by using the
`--repo`
parameter (may be specified multiple
You can avoid changing the
`rev`
to an unexpected value by using the
`--repo`
parameter (may be specified multiple
times), to explicit
list repositories that should be updated. An option to explicit
exclude
times), to explicit
ly list repositories that should be updated. An option to explicitly
exclude
repositories
[
will not be implemented
](
https://github.com/pre-commit/pre-commit/issues/1959
)
into
`pre-commit`
.
repositories
[
will not be implemented
](
https://github.com/pre-commit/pre-commit/issues/1959
)
into
`pre-commit`
.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment