yasmaryhd

This is a reference for using GitHub as a project management tool. I will be using GitHub's beta project which has slightly different functionality than the default project.

Issues

For those that have used other project management tooling, issues are akin to JIRA stories or trello cards. Per GitHub's own definition: Use GitHub Issues to track ideas, feedback, tasks, or bugs for work on GitHub. Think of an issue as the place to track work (e.g. development) that is happening within the project.

Creating issues

Issues are scoped to a repository. Knowing this will help you figure out which of the following paths will be most convenient for managing them.

The Apps Script CLI, or clasp, is a tool that lets you to create, edit, and deploy Apps Script projects locally. It allows you to create and publish web apps and add-ons for products like Sheets, Docs, Forms, and Slides from the command line. There are two ways you can develop Apps Script, using script.google.com or locally on your computer. Repo: https://github.com/google/clasp

Prerequisites

Node.js >= v6.0.0: install via homebrew or direct download
Google Account: will be used to authenticate with clasp. If a GCP project will be used, this account should have access to it.
Enable Apps Script API: Log into your Google Account and navigate to https://script.google.com/home/usersettings.

Background

The OAuth consent screen is a prompt that appears when a user is asked to grant or deny access to their data by an app. The screen includes: A summary of the project, The project's policies, and The requested authorization scopes of access.

Within GCP, the OAuth consent screen contains branding information for users and is known as a brand. Brands can be limited to internal users or public users. An internal brand makes the OAuth flow accessible to someone who belongs to the same Google Workspace organization as the project. source.

OAuth Consent screen can be accessed via url: https://console.cloud.google.com/apis/credentials/consent?project=[replace-with-your-project-id]

The problem

Background

The following is a step by step guide for copying over a subdirectory of an existing GH repository into a new repository, which also includes the git history.

Steps

1) Clone the source repo

NOTE: The tool we will be using in step 2 requires a fresh clone. If you want to use a specific version, you can run command in step 2 with a --force command.

	import os
	import re
	import csv
	from collections import defaultdict
	from datetime import datetime

	"""
	This script searches for roles assigned to specific Google groups in Terraform (.tf) files
	and outputs a CSV file with the results.