Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P puppet-tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • emmapeel
  • puppet-tails
  • Repository
  • puppet-tails
  • files
  • gitolite
  • install_remotes.sh
Find file Blame History Permalink
  • Zen Fu's avatar
    Use correct credentials when pushing from weblate-gatekeeper (gitlab-migration#74) · ce563cc9
    Zen Fu authored Jul 22, 2020
    Pushes from weblate-gatekeeper should be done as the
    "role-weblate-gatekeeper" GitLab user, and for that we need to use a
    specific SSH key when pushing.
    
    This commit adds a new "Host" in gitolite's SSH config and changes the
    remote URL of the gatekeeper repo to use the that new host, thus making
    use of the correct key to connect to GitLab.
    
    See: https://salsa.debian.org/tails-team/gitlab-migration/-/issues/74
    ce563cc9