Title: Pinned versions compete at different scopes · Issue #1748 · pre-commit/pre-commit · GitHub
Open Graph Title: Pinned versions compete at different scopes · Issue #1748 · pre-commit/pre-commit
X Title: Pinned versions compete at different scopes · Issue #1748 · pre-commit/pre-commit
Description: In #863, I reported an issue where stable of black didn't work as expected. That issue is biting me again today. Somewhere in a cryptic cache, pre-commit has cached that stable is something other than what Github has as stable for the sa...
Open Graph Description: In #863, I reported an issue where stable of black didn't work as expected. That issue is biting me again today. Somewhere in a cryptic cache, pre-commit has cached that stable is something other t...
X Description: In #863, I reported an issue where stable of black didn't work as expected. That issue is biting me again today. Somewhere in a cryptic cache, pre-commit has cached that stable is something oth...
Opengraph URL: https://github.com/pre-commit/pre-commit/issues/1748
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Pinned versions compete at different scopes","articleBody":"In #863, I reported an issue where `stable` of black didn't work as expected. That issue is biting me again today.\r\n\r\nSomewhere in a cryptic cache, `pre-commit` has cached that `stable` is something other than what Github has as `stable` for the same repo. Is there any way to tell what commit pre-commit has associated with `stable`?\r\n\r\nThe recommendation is to \"just use autoupdate\". However, that recommendation requires committing the updated version to the current project's repo, irrespective of what version that project might be using in the test suite or what version of black may be installed in the development environment.\r\n\r\nMoreover, because autoupdate writes to a SCM-managed file, running that command alters the state of the environment, demanding additional manual steps (config), and diverging that file from its previous state. For example, I manage [this pre-commit config](https://github.com/jaraco/skeleton/blob/main/.pre-commit-config.yaml) that's shared across hundreds of projects, so if black needs updating, I need to update it in that root repository before merging it with the hundred projects.\r\n\r\nI'd like to find a way to eliminate the toil and noise of keeping pinned versions updated across hundreds of projects.\r\n\r\nI'd rather there be a way to specify \"latest\" for each of the plugins and while pre-commit should continue to cache those values for performance, there should be a way to say, \"please check\" and ideally that could happen periodically (~daily or weekly) for a given repo.\r\n\r\nMaybe the best thing to do for now is to just `rm -r ~/.cache/pre-commit` each time I get divergent results from what `black` produces from other updated sources?","author":{"url":"https://github.com/jaraco","@type":"Person","name":"jaraco"},"datePublished":"2020-12-30T02:25:07.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/1748/pre-commit/issues/1748"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:6f0664c2-e5a0-461d-55ed-8575af9e7d0d |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | BB7E:31348B:2446A0:31B5B6:6A5590C1 |
| html-safe-nonce | 8ae8033bab32028a948602ca18abfaa797bda27dbd11d079fbd61ae839f45072 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCQjdFOjMxMzQ4QjoyNDQ2QTA6MzFCNUI2OjZBNTU5MEMxIiwidmlzaXRvcl9pZCI6IjQyMTAyNDkzOTQyODc5MDcwMDkiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | e39e4a3745f1046d985bac2e48ced1b9c3bc6e0e185ab98ea93e30545cdb67fd |
| hovercard-subject-tag | issue:776167092 |
| github-keyboard-shortcuts | repository,issues,commits,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/pre-commit/pre-commit/1748/issue_layout |
| twitter:image | https://opengraph.githubassets.com/c89c8e8f4e1517b11e02cd4a647c583a6b0c5ea41e0b35d5072897e908a2e11f/pre-commit/pre-commit/issues/1748 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/c89c8e8f4e1517b11e02cd4a647c583a6b0c5ea41e0b35d5072897e908a2e11f/pre-commit/pre-commit/issues/1748 |
| og:image:alt | In #863, I reported an issue where stable of black didn't work as expected. That issue is biting me again today. Somewhere in a cryptic cache, pre-commit has cached that stable is something other t... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | jaraco |
| hostname | github.com |
| expected-hostname | github.com |
| None | b5665c84831ed9ac4fb79519c16c9c5580ba8092fb8bb6e3e72972ec7197348e |
| turbo-cache-control | no-preview |
| go-import | github.com/pre-commit/pre-commit git https://github.com/pre-commit/pre-commit.git |
| octolytics-dimension-user_id | 6943086 |
| octolytics-dimension-user_login | pre-commit |
| octolytics-dimension-repository_id | 17689377 |
| octolytics-dimension-repository_nwo | pre-commit/pre-commit |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 17689377 |
| octolytics-dimension-repository_network_root_nwo | pre-commit/pre-commit |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | aa21baa44893467b0b640d0300538f84ca8c475b |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width