Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

What can Administrative department use GitHub for?

GitHub allows ...

Why do I need to use GitHub?

Simple ....

How to securely leverage GitHub?

Syracuse University IT users of GitHub should ensure that they enable the highest level of security to protect the information they are storing in GitHub .  The way to do that is to enable the use of "Passkeys" to login to GitHub.  Many of the IT users on campus already possess a physical FIDO2 complaint "Passkey" device in the form of their YubiKey Smartcard and it can be used as the physical "Passkey" device for GitHub.  Learn More

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


Additional Tips

Import Repositories

Code itself, including branches, and commit history can be imported using the GitHub import tool. In Gitlab create a personal access with read only abilities and when prompted give the GitHub form your username and the GitLab token. Note: does not import non-core-git things like CI/CD setup.   

https://github.com/new/import  

Importing CI/CD

From Gitlab: Gitlab and GitHub use different syntax for structuring CI/CD pipelines, in GitHub called “actions ”. These are incompatible, and require the use of GitHub Action  importer to translate or be re-written.   

The GitHub Action Importer   can read in CI/CD pipelines but it’s not perfect.   

The importer requires an GitHub access token with write access to the repositories you want and your Gitlab token (read access only).   

The setup can take some time but once setup it works. Unfortunately, it does not auto load secret keys values and they have to be manually created. Many of the repos use docker login to log into GitLab docker repository and build the project and to push them . This action, at least the pushing and receiving is here: https://github.com/docker/login-action and it may be worth to just rebuild the simpler ones instead of re-doing actions.