Python script to get all the programming languages in a GitHub organization and return a total number of repos using the programming language.
Hard requirements: 🐍
read:org and repo:status permissions. 🔐
| Para CPF | |
| /^\d{3}\.\d{3}\.\d{3}\-\d{2}$/ | |
| Para CNPJ | |
| /^\d{2}\.\d{3}\.\d{3}\/\d{4}\-\d{2}$/ | |
| Para ambos ao mesmo tempo |
This playbook is a step-by-step guide to assist you with migration from GitLab to GitHub.com Enterprise Cloud GHEC.
| Steps & Tasks | Description |
|---|---|
| Step One | Let's get ready for the migration. This step gives you an overview of what is required to start the migration process |
| Step Two | Creating the artefact to be imported on GitHub requires special access to the Enterprise Cloud Import tool. This step will help you understand what is required to get access to the tool. |
| Step Three | With the file ready to be imported, this step will guide you on how to connect and upload the file to your GitHub Enterprise Cloud instance. |
Managing multiple repositories that serve distinct but interconnected purposes can be a challenging task 😓. This scenario is common when an organization wishes to contribute to an open-source project 🌐 while also maintaining an internal space for private collaboration 🔒.
The challenge here lies in keeping these repositories in sync 🔄 without manual intervention, ensuring that changes made to one repository 📁 are accurately reflected in the other 📁.
In this step-by-step tutorial 📃, we'll walk through a use case where a customer wants to contribute to an open-source project 💻 and, at the same time, collaborate internally within their organization 🏢.
We will:
Based on https://docs.getutm.app/guides/windows/
brew install aria2 cabextract wimlib cdrtools minacle/chntpw/chntpw;bash uup_download_macos.sh - this will produce an ISO;
| #!/bin/bash | |
| # Make sure you change this script chmod to executable | |
| # Set your GitHub username and access token | |
| USERNAME={REPLACE_ME} | |
| ACCESS_TOKEN={REPLACE_ME} | |
| # Set the path to the directory where you want to store your repositories | |
| LOCAL_REPO_DIR=/path/to/your/local/repo/directory |
One of the biggest issues with using a self hosted GitHub runner is that actions that require downloading large amounts of data will bottleneck at the network. [actions/cache][1] does not support locally caching objects and artifacts stored on GitHub's servers will require a lot of bandwidth to fetch on every job. We can, however, set up a content proxy using [Squid][2] with SSL bumping to locally cache requests from jobs.
A major challenge is that [actions/cache][1] uses Azure storage APIs which makes HTTP range requests. While Squid supports range requests, it is not good at caching them. There is an option, range_offset_limit none which, according to the [documentation][3]:
A size of 'none' causes Squid to always fetch the object from the beginning so it may cache the result. (2.0 style)
However, after extensive debugging, I discovered that the feature does not work if the client closes the connection. When range_offset_limit is set, Squid will make a full request to the server,
| #!/usr/bin/env python | |
| import sys | |
| import time | |
| import paramiko | |
| ## How to use it? | |
| ## | |
| ## You have to install a dependecy called paramiko, which is a ssh protocol implementation that helps you to connect to sftp. | |
| ## pip install paramiko | |
| ## Commands in your terminal: |
Because the customer uses infrastructure as a code (IaC) into their pipelines using AWS CloudFormattion, they were used to the YAML format and the advanced features from the AWS schema and functionalities available, Actions YAML was simple to use and teach, however, introduced last year the workflow_dispatch allows customers to create workflows that are manually trigger with the option of input parameters. Our product supports only a limit of 10 inputs and throws an error, not allowing customer with multi-cloud environment setup more control for those manually trigger workflows.
We introduced a few options for the customer with the goal of continue maintaining the developer experience, interoperability, compliance and security and the ability to use the product in a multi-cloud environment.
Populating this as we dig further into the platform, hopefully it'll be as useful to you as it is to use.