Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
py-heptapod
py-heptapod
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • py-heptapodpy-heptapod
  • Merge Requests
  • !14

Closed
Opened Mar 01, 2020 by Georges Racinet@gracinet🦑Owner
  • Report abuse
Report abuse

Using a new ad-hoc protocol in Git hook payload

  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 1

For heptapod#208 (closed), we need a clean way to distinguish between our internal Git pushes from Mercurial (legit) and bogus attempts to use Git against Mercurial projects.

Assignee
Assign to
Reviewer
Request review from
Version 0.8.4
Milestone
Version 0.8.4
Assign milestone
Time tracking
Reference: heptapod/py-heptapod!14
Source branch: topic/heptapod-0-8/internal-hook-protocol