Versions Compared

Key

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

What can

Administrative

an administrative department use GitHub for?

GitHub allows ...Using GitHub for administrative purposes involves leveraging its features to manage and coordinate various aspects of a project or organization. 

Why do I need to use GitHub?

Simple ...In summary, using GitHub for administrative purposes means organizing and managing documentation, tasks, and collaboration more efficiently, while also benefiting from version control, access control, and integrations with other tools.

  1. Repository Management: Create and manage repositories for storing and organizing project documents, policies, or any other relevant materials. This can include everything from organization policies to project plans.

  2. Version Control: Use Git for tracking changes in documents and code, allowing multiple users to work on the same files simultaneously without losing prior versions. This is particularly useful for maintaining the integrity and history of important documents.

  3. Project Boards: Implement project boards to organize and prioritize work. This is akin to tools like Trello, where you can have columns for to-do, in progress, and done tasks, making it easier to visualize the workflow and progress.

  4. Collaboration and Communication: Use Pull Requests for proposing changes and enabling discussions around those changes. This fosters a collaborative environment where team members can review, discuss, and contribute to each other's work.

  5. Documenting Procedures and Policies: Utilize the wiki feature or README files in repositories to document procedures, policies, and guidelines. This ensures that important information is easily accessible and maintainable.

  6. Automations and Integrations: Leverage GitHub Actions and other integrations for automating administrative tasks like sending notifications, updating statuses, or syncing with other tools (like Slack, email, or project management tools).

  7. Access Control and Security: Manage access to repositories and control who can read, write, or administer your organizational materials. This is crucial for maintaining the security and confidentiality of sensitive information.

  8. Data Analytics and Insights: Use GitHub's analytics and insights features to track contributions, review activities, and understand work patterns within your team or organization.


How to get started


Additional Information

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.