As we reevaluate how to best support and maintain Staging Ref in the future, we encourage development teams using this environment to highlight their use cases in the following issue: https://gitlab.com/gitlab-com/gl-infra/software-delivery/framework/software-delivery-framework-issue-tracker/-/issues/36.

Skip to content
Snippets Groups Projects
Commit 44601bac authored by Sytse Sijbrandij's avatar Sytse Sijbrandij
Browse files

Better comments in the git hooks and give workaround.

parent cc193ea4
No related branches found
No related tags found
No related merge requests found
#!/usr/bin/env ruby
# This file was placed here by GitLab. It makes sure that your pushed commits
# will be processed properly.
# You can add your own hooks to this file, but be careful when updating gitlab-shell!
# This file was placed here by GitLab Shell.
# It is a shared file that is symlinked from all repositories.
# It makes sure that your pushed commits will be processed properly.
# You can add your own hooks to by uncommenting the lines at the bottom.
# If you upgrade GitLab Shell you will have to redo your changes.
# Consider using project services of post-receive hooks
# See http://doc.gitlab.com/ce/integration/README.html
# Or use web hooks that trigger an external application
# See http://doc.gitlab.com/ce/web_hooks/web_hooks.html
changes = ARGF.read
key_id = ENV['GL_ID']
Loading
Loading
@@ -15,3 +21,12 @@ if GitlabPostReceive.new(repo_path, key_id, changes).exec
else
exit 1
end
## How to add a custom hooks to some repositories:
## 1) Put a file with custom code in the repository root directory.
## 2) Uncomment the lines below.
## 3) Replace 'project-specific-hook' with the name if the custom file.
#
# if File.exists?('project-specific-hook')
# execute 'project-specific-hook'
# end
#!/usr/bin/env ruby
# This file was placed here by GitLab. It makes sure that your pushed commits
# will be processed properly.
# You can add your own hooks to this file, but be careful when updating gitlab-shell!
# This file was placed here by GitLab Shell.
# It is a shared file that is symlinked from all repositories.
# It makes sure that your pushed commits will be processed properly.
# You can add your own hooks to by uncommenting the lines at the bottom.
# If you upgrade GitLab Shell you will have to redo your changes.
# In GitLab Enterprise Edition you can use Git Hooks instead.
# See http://doc.gitlab.com/ee/git_hooks/git_hooks.html
refs = ARGF.read
key_id = ENV['GL_ID']
Loading
Loading
@@ -15,3 +19,12 @@ if GitlabAccess.new(repo_path, key_id, refs).exec
else
exit 1
end
## How to add a custom hooks to some repositories:
## 1) Put a file with custom code in the repository root directory.
## 2) Uncomment the lines below.
## 3) Replace 'project-specific-hook' with the name if the custom file.
#
# if File.exists?('project-specific-hook')
# execute 'project-specific-hook'
# end
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment