Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Merge requests
  • !555

Merged
Created 13 years ago by Administrator@rootOwner

Allow custom post-receive hook

  • Overview 6
  • Commits 0
  • Changes 0

Created by: netdata-be

This pull request solves issue #476

Loading
Loading

  • Administrator
    Administrator @root · 13 years ago
    Owner

    Created by: ariejan

    I've added some in-code comments on your commits. Please check them out before merging this.

    By Administrator on 2012-03-15T10:14:37 (imported from GitLab project)

  • Administrator
    Administrator @root · 13 years ago
    Owner

    Created by: netdata-be

    Can you please review again? I have also fixed a permission problem in this commit

    By Administrator on 2012-03-15T13:14:56 (imported from GitLab project)

  • Administrator
    Administrator @root · 13 years ago
    Owner

    Created by: dzaporozhets

    @ariejan i've assigned this one to you

    By Administrator on 2012-04-03T15:50:34 (imported from GitLab project)

  • Administrator
    Administrator @root · 13 years ago
    Owner

    Created by: dubcanada

    Should this not be project specific rather then global?

    By Administrator on 2012-04-04T19:03:15 (imported from GitLab project)

  • Administrator
    Administrator @root · 13 years ago
    Owner

    Created by: netdata-be

    the way I do it is 100% the same as gitolite recommends it. To be able to make it project specific they advice to use git config options which is also supported by gitolite. There is also an other enhancement request to implement custom config options.

    But you could implement it in an other fashion.

    By Administrator on 2012-04-04T19:21:24 (imported from GitLab project)

  • Administrator
    Administrator @root · 13 years ago
    Owner

    Created by: dubcanada

    Not really knowing how this works. From what I see.

    1. It processes the regular resque stuff in the while loop.
    2. Then it goes on to process anything in post-secondary-hooks?

    Is that correct? I also assume it would post the same stuff, so you could do a ton of if statements in the post-secondary-hooks if you want to separate functionality for each project?

    If that's correct I don't really see any problem with not having project specific stuff, if that is what gitolite recommends.

    By Administrator on 2012-04-04T19:31:05 (imported from GitLab project)

  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
Assign to
0 Reviewers
Request review from
Milestone
No milestone
None
None
Time tracking
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Lock merge request
Unlocked
participants
Reference:
Source branch: github/fork/netdata-be/master

    0 pending comments

Menu

Projects Groups Snippets
Help