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

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • idrozdov/gitlab-shell
  • mmj/gitlab-shell
2 results
Show changes
Commits on Source (2)
#!/usr/bin/env ruby #!/usr/bin/env ruby
# This file was placed here by GitLab. It makes sure that your pushed commits # This file was placed here by GitLab Shell.
# will be processed properly. # It is a shared file that is symlinked from all repositories.
# You can add your own hooks to this file, but be careful when updating gitlab-shell! # It makes sure that your pushed commits will be processed properly.
# For instructions on how to add custom hooks see the comment below.
# 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 changes = ARGF.read
key_id = ENV['GL_ID'] key_id = ENV['GL_ID']
Loading
@@ -11,6 +16,15 @@ repo_path = Dir.pwd
Loading
@@ -11,6 +16,15 @@ repo_path = Dir.pwd
require_relative '../lib/gitlab_post_receive' require_relative '../lib/gitlab_post_receive'
if GitlabPostReceive.new(repo_path, key_id, changes).exec if GitlabPostReceive.new(repo_path, key_id, changes).exec
## 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.
## 4) If you upgrade GitLab Shell you will have to redo your changes.
#
# if File.exists?('project-specific-hook')
# execute 'project-specific-hook'
# end
exit 0 exit 0
else else
exit 1 exit 1
Loading
Loading
#!/usr/bin/env ruby #!/usr/bin/env ruby
# This file was placed here by GitLab. It makes sure that your pushed commits # This file was placed here by GitLab Shell.
# will be processed properly. # It is a shared file that is symlinked from all repositories.
# You can add your own hooks to this file, but be careful when updating gitlab-shell! # It makes sure that your pushed commits will be processed properly.
# For instructions on how to add custom hooks see the comment below.
# In GitLab Enterprise Edition you can use Git Hooks instead.
# See http://doc.gitlab.com/ee/git_hooks/git_hooks.html
refs = ARGF.read refs = ARGF.read
key_id = ENV['GL_ID'] key_id = ENV['GL_ID']
Loading
@@ -11,7 +14,17 @@ repo_path = Dir.pwd
Loading
@@ -11,7 +14,17 @@ repo_path = Dir.pwd
require_relative '../lib/gitlab_access' require_relative '../lib/gitlab_access'
if GitlabAccess.new(repo_path, key_id, refs).exec if GitlabAccess.new(repo_path, key_id, refs).exec
## 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.
## 4) If you upgrade GitLab Shell you will have to redo your changes.
#
# if File.exists?('project-specific-hook')
# execute 'project-specific-hook'
# end
exit 0 exit 0
else else
exit 1 exit 1
end end