Gianfranco Reppucci giefferre

Generate GitHub Enterprise Issue from Google Form submission

To generate a nicely-formatted GitHub issue (even for GitHub Enterprise accounts) from a Google Form submission, you can use Google's script editor along with a GitHub personal access token that connects to the API. This is particularly useful when you need to triage bugs or feature requests directly to developers, but those who are submitting issues do not have access to your GitHub Enterprise instance.

Once this is up and running, on the development end, you can do some cool things within the body of each issue, like automatically closing GitHub issues via your commit messages and CCing your dev group or individual team members for each issue.

Here's how to set it up.

Step 1: Create Your Form

Go to Google Drive and create a form with fields
Click the Responses tab

Elasticsearch: updating the mappings and settings of an existing index

Note: This was written using elasticsearch 0.9.

Elasticsearch will automatically create an index (with basic settings and mappings) for you if you post a first document:

$ curl -X POST 'http://localhost:9200/thegame/weapons/1' -d \
'{
  "_id": 1,

	> You are Kipi Setup Assistant.
	>
	> Greet the user warmly and introduce yourself:
	> "Hi! I'm going to help you set up Kipi — your Core-Knowledge Keeper. Kipi is an AI agent that builds and maintains deep, structured documentation for your project so that anyone — even someone who has never seen the codebase — can understand, fix, or rebuild it."
	>
	> Then, check for BMAD:
	> Look for a _bmad/ directory in the project root.
	> - If found: Say "I see you already have BMAD installed — great! I'll use the BMAD framework to build Kipi with full compliance."
	> - If not found: Say:
	> "Before we continue, I noticed you don't have the BMAD Method installed in this project. I strongly recommend setting it up first — BMAD provides the framework that Kipi is built on, including structured agent patterns, menu systems, workflows, and compliance validation. It will make Kipi much more robust and maintainable.

	acm-pca:CreateCertificateAuthority
	aws-marketplace:AcceptAgreementApprovalRequest
	aws-marketplace:Subscribe
	backup:PutBackupVaultLockConfiguration
	bedrock:CreateProvisionedModelThroughput
	bedrock:UpdateProvisionedModelThroughput
	devicefarm:PurchaseOffering
	dynamodb:PurchaseReservedCapacityOfferings
	ec2:ModifyReservedInstances
	ec2:PurchaseCapacityBlock

	vi /etc/environment

	add these lines...

	LANG=en_US.utf-8
	LC_ALL=en_US.utf-8

	#!/usr/bin/env python
	import argparse
	import redis


	def connect_redis(conn_dict):
	conn = redis.StrictRedis(host=conn_dict['host'],
	port=conn_dict['port'],
	db=conn_dict['db'])
	return conn

	// Reference: http://www.blackdogfoundry.com/blog/moving-repository-from-bitbucket-to-github/
	// See also: http://www.paulund.co.uk/change-url-of-git-repository

	$ cd $HOME/Code/repo-directory
	$ git remote rename origin bitbucket
	$ git remote add origin https://github.com/mandiwise/awesome-new-repo.git
	$ git push origin master

	$ git remote rm bitbucket