GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Let hook authors define branch to update from · Issue #2508 · pre-commit/pre-commit

Let hook authors define branch to update from #2508

New issue
Copy link
New issue
Copy link
Closed
Closed
Let hook authors define branch to update from#2508
Copy link
Labels
upstream-bug

Description

@finswimmer
finswimmer
opened on Sep 9, 2022
Issue body actions

Hey,

at the moment pre-commit autoupdate looks for the most recent tag in the default branch of the repository. This works well, for repository where new releases are tagged in the default branch.

I common branching strategy is, that the default branch is the active development branch, commits get backported to stable release branches and new releases are tagged in this stable release branches. At the moment pre-commit is unable to find the most recent release, due to tags are not given in the main branch.

This is why I suggest a new option, that hooks authors can put into their .pre-commit-hooks.yaml in the default branch, for defining a branch in which pre-commit autoupdate should look for the most recent tag.

Something similar is done by renovate with the baseBranches option.

Thanks a lot.

fin swimmer

Activity

  1. asottile commented on Sep 9, 2022

    @asottile
    asottile
    on Sep 9, 2022
    Member
    More actions

    no thanks, tags should be on the primary branch

    it's trivial to merge a tag into such a branch and is a common way to denote that there's a release

    you're burying the lede a bit, this is motivated by poetry having a very non standard release workflow

  2. asottile
    closed this as completedon Sep 9, 2022
  3. asottile
    added
    upstream-bug
    on Sep 9, 2022
  4. pre-commit
    locked as resolved and limited conversation to collaborators on Sep 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    upstream-bug

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.