Skip to content

GitLab

  • Menu
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
  • Issues
  • #8247

Closed
Open
Created Nov 04, 2014 by Administrator@rootOwner

[IMPRV] Clarify 'SSH keys required message'

Created by: danielsokolowski

The message "You won't be able to pull or push project code via SSH until you add an SSH key to your profile" should include information that pushing using HTTPS does NOT require setting up SSH keys.

This was not obvious to me and so also might not be to others. In my situation the implication that over 30+ users would have go through this setup process was negatively impacting our review.

How about, making the HTTPS be the default option and when user clicks on SSH the message then appears. (below the repo links) - just my humble observation.

suggested improvement for SSH keys setup needed

Assignee
Assign to
Time tracking