Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Welcome abpedroni #3

Open
github-actions bot opened this issue Mar 12, 2022 · 3 comments
Open

Welcome abpedroni #3

github-actions bot opened this issue Mar 12, 2022 · 3 comments
Labels
automated issue awaiting-approval documentation Improvements or additions to documentation report

Comments

@github-actions
Copy link

🎯 Purpose

The purpose of this guide is to give you the basic information you need to get going with GitHub. This guide is intended to be used for GitHub in a common configuration. It is not the end all and be all of the information available to help you succeed with GitHub, but is a curated list of the following GitHub resources as well as other public sources of information:

Example how to link to additional markdown files in the same repository

:octocat: The GitHub Platform

GitHub is more than "version control"; it is an all-inclusive and unified collaboration platform:


image

⏩ Get Going!

* ENTERPRISE ONLY

💻 Get Distributed

Get familiarized with why modern distributed version control is an improvement over traditional centralized version control

⚙️ Get Installed *

Get your GitHub Enterprise instance installed and on a virtualization platform of your choice

🔧 Get Configured *

Get your GitHub Enterprise instance configured with the right authentication and backup infrastructure for your environment

📁 Get Organized

Get your people and code organized to optimize discoverability and reuse

  • Organizing People for Successful Collaboration (5 min video)

  • Why organization structure matters

    • The immediate instinct may be to create an organization for every project or department at your company, leading to many divided groups that function in GitHub as siloes

    • This may seem like a good way to manage permissions and reduce noise, but it’s not always the ideal strategy

    • In fact, it is detrimental to cross-team collaboration and can result in administrative headaches down the line

    • Instead of creating many organizations and siloing users, we suggest using one or few organizations for shared ownership of repositories and making use of teams to segment users within those organizations -- e.g.: Google; Microsoft

      image

🔑 Get Access

Get access and permissions in place to satisfy your security policies

🔩 Get Setup

Get Git and GitHub setup for the first time

🌊 Get Flowing

Get your work flowing to the right people and reviewed by the right people

image

✅ Get Managing

Get your work and projects managed from start to finish

📚 Get Documented

Get information about your work and projects documented to share right next to your code

🔗 Get Integrated

Get integrated with the rest of your development pipeline

📢 Get Informed

Get informed on what's new with GitHub

⬆️ Get Upgraded *

Get your GitHub Enterprise instance upgraded to the latest release

ℹ️ Get Enabled

Get enabled on the basics of Git and GitHub

🆘 Get Help

Get dedicated help from GitHub to support your continued success

Get help from the GitHub community

🌐 Get Open Sourcing

Get collaborating with the Open Source community
@abpedroni abpedroni added the documentation Improvements or additions to documentation label Mar 12, 2022
@abpedroni
Copy link
Owner

/rebase

@abpedroni
Copy link
Owner

TODO

testando

@abpedroni
Copy link
Owner

TODO testando

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
automated issue awaiting-approval documentation Improvements or additions to documentation report
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@abpedroni