You need to post the list of changed refs to redis using the right namespace (and a valid user) See: https://gitlab.com/gitlab-org/gitlab-shell/blob/master/lib/gitlab_post_receive.rb#L69 for how it is done for post_receive
On Friday, April 8, 2016 at 5:46:01 AM UTC-7, Alexander Kitaev wrote: > > Hello, > > We're developing SubGit - a tool for mirroring SVN project to Git > repositories. Many of SubGit users use it with GitLab (see > http://subgit.com/gitlab). > > It all works just find, but there is one standing issue with that > integration, that we'd like to fix. > We'd like get GitLab devs advice on what would be the best way fix it. > > Issue description: > > - SubGit runs periodical job to fetch new changes from SVN project and > apply those to the Git repository. > - When doing so and creating new commits in Git repository, Git hooks > (pre/post-receive) are not ran. > - As hooks are not ran, GitLab doesn't have a chance to update or > invalidate its caches and GitLab web UI doesn't display newly created > commits. > - New commits are displayed only after user pushes to repository from Git. > > What would be the best way to resolve this issue? > > Is there an API call SubGit could use to tell GitLab that Git repository > was externally changed? > Or would it be safe to call GitLabe pre-receive hook with the refs deltas > that already present in repository? Would that result in cache update? > > Thanks a lot in advance for your help! > > With best regards, > Alexander Kitaev. > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/dc3f3024-fabc-4d65-bc89-9f8220f203f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
