Docs: Guidelines for how to document Git commands

We have Git content outside of the Learn Git area of the left nav.

What should we do with this content? Should we have Git content outside of that area?

• If so, can we come up with a standard way of formatting it so it's easy to consistently find?
• If not, let's figure out where it will go and how it should be formatted.

List of examples:

• https://docs.gitlab.com/ee/user/project/#create-a-new-project-with-git-push
• https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html#when-you-use-git-commands-locally
• https://docs.gitlab.com/ee/user/project/merge_requests/allow_collaboration.html#push-to-the-fork-as-the-upstream-member
• https://docs.gitlab.com/ee/user/project/merge_requests/conflicts.html#from-the-command-line
• https://docs.gitlab.com/ee/user/project/merge_requests/cherry_pick_changes.html#from-the-command-line
• https://docs.gitlab.com/ee/user/project/merge_requests/revert_changes.html#revert-a-merge-commit-to-a-different-parent-commit
• https://docs.gitlab.com/ee/topics/git/lfs/
• https://docs.gitlab.com/ee/user/project/issues/crosslinking_issues.html#from-commit-messages
• https://docs.gitlab.com/ee/user/project/repository/files/git_blame.html#associated-git-command
• https://docs.gitlab.com/ee/user/project/repository/files/git_history.html#in-the-cli
• https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#from-the-command-line
• https://docs.gitlab.com/ee/user/project/repository/reducing_the_repo_size_using_git.html#purge-files-from-repository-history
• https://docs.gitlab.com/ee/user/project/file_lock.html - has to do with LFS
• https://docs.gitlab.com/ee/user/project/repository/signed_commits/ - These topics are all about signing your Git commits--there is one for the UI, but maybe this goes in the Git area?
• https://docs.gitlab.com/ee/ci/git_submodules.html - split? the first part is not about CI/CD

I wonder if this might also go under Git? Hmmm. It's required.. but it's not really about learning Git. Just putting here for consideration. https://docs.gitlab.com/ee/user/ssh.html

This issue is to determine what to do and to document the guidelines.

Maybe the standard is:

• When it's about learning a command, outside of using a GitLab feature, it can be outside the Learn Git section, but it needs to have a standard format... (for the title at least)
• The Learn GitLab section is specifically for teaching commands that don't correspond to features?

Not sure that would be possible..