Skip to content

A new branch raise an error even if the job is done #3755

@tst2005

Description

@tst2005
  • Gitea version (or commit ref): 1.4.0 (final release) (issue initially got on 1.4.0rc3)
  • Git version: 2.1.4
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Done on any repo (test made on a fresh new repo, after the initial commit)

  1. I'm creating a "new file" (named test.md) in a "new branch" (a banch named test) with a commit message test
  2. I got the following error message, with a HL on the filename (like a bad file name)
PushUpdate: newCommit.CommitsBeforeLimit: exit status 129 - error: unknown option `contains' usage: git for-each-ref [options] [] -s, --shell quote placeholders suitably for shells -p, --perl quote placeholders suitably for perl --python quote placeholders suitably for python --tcl quote placeholders suitably for tcl --count show only matched refs --format format to use for the output --sort field name to sort on
  1. in fact the branch test successfully is created.

It seems a "post-*" hook issue.

Screenshots

  1. and 2. create a new file in a new branch

  2. the-branch-is-created

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions