Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

What an IT use GitHub for?

GitHub allows you to create, store, change, merge, and collaborate on files or code. Any member of a team can access the GitHub repository (think of this as a folder for files) and see the most recent version in real-time. Then, they can make edits or changes that the other collaborators also see.  The files can be source code for applications or scripts being created or maintained by the Team or simply configuration files or build steps used to setup and administer a service or application.

Why do I need to use GitHub?

Simple answer is version control.  Version control is important as it makes collaboration more transparent and reproducible. By visibly tracking iterative changes, you and your Team can experiment with new approaches knowing that you can revert to the original as needed. 

Can I use GitHub to make tasks easier to accomplish?

GitHub has GitHub Actions that allow for automation and Continuous Integration & Continuous Delivery (CI/CD) to be used with your Team's repositories. Learn More


How to get started

Create Team

  • Once logged into Syracuse University's instance is to create a GitHub Team - Create Team
    • To enable easier collaboration and discovery in the platform ITS users should name their Team based on the following naming convention: "ITS-(Department/Team Name/Acronym)-(Role if required)". e.g. "ITS-CIS"
    • "Visible" teams are recommended so that collaboration can be made easier and requests to join can be made.
    • Nested Teams are not recommended since the relationship of a child team to its parent may result in users having access to a repository that you did not intend.  If there is a new group of people working on a repository, create another Team.
    • In some situations, you may want to create separate Teams for differencing level of access to the Team's repositories.  For example, it may be required to create a Team named "ITS-IAM-Admins" to provide a smaller scope of user access to the Admin role of the Team's repositories instead of the whole "ITS-IAM" team.
  • Setup Team Maintainers so that requests to join the Team can be approved - Setup Maintainers
    • There should be at least two group maintainers so that if one person is unavailable another Team member can perform the administrative duties of Team maintenance.
  • Publicize your Team's GitHub URL so that other members of your department can join the GitHub Team.


Crete Repository

  • No labels