Gesugao-san

Demo:

Spoiler warning

Spoiler text. Note that it's important to have a space after the summary tag. You should be able to write any markdown you want inside the <details> tag... just make sure you close <details> afterward.

console.log("I'm a code block!");

Markdown Text 101

Want to inject some flavor into your everyday text chat? You're in luck! Discord uses Markdown, a simple plain text formatting system that'll help you make your sentences stand out. Here's how to do it! Just add a few characters before & after your desired text to change your text! I'll show you some examples...

What this guide covers:

Text Formatting
Organizational Text Formatting
- Headers
Subtext

Redirecting GitHub Pages after a repository move

The problem

You have a repository, call it alice/repo. You would like to transfer it to the user bob, so it will become bob/repo.

However, you make heavy use of the GitHub Pages feature, so that people are often accessing https://alice.github.io/repo/. GitHub will helpfully redirect all of your repository stuff hosted on github.com after the move, but will not redirect the GitHub Pages hosted on github.io.

The solution

⚠️ This gist is no longer updated! For maintained, improved and even more extended guide click here.

How to use Discord Webhook

It's a JSON

First, learn JSON. It's not programming language, not even close. Just follow syntax rules and you will be fine.

Working with git remotes on Heroku

Generally, you will add a git remote for your Heroku app during the Heroku app creation process, i.e. heroku create. However, if you are working on an existing app and want to add git remotes to enable manual deploys, the following commands may be useful.

Adding a new remote

Add a remote for your Staging app and deploy

Note that on Heroku, you must always use master as the destination branch on the remote. If you want to deploy a different branch, you can use the syntax local_branch:destination_branch seen below (in this example, we push the local staging branch to the master branch on heroku.

$ git remote add staging https://git.heroku.com/staging-app.git

	udp://public.popcorn-tracker.org:6969/announce
	http://182.176.139.129:6969/announce
	http://5.79.83.193:2710/announce
	http://91.218.230.81:6969/announce
	udp://tracker.ilibr.org:80/announce
	http://atrack.pow7.com/announce
	http://bt.henbt.com:2710/announce
	http://mgtracker.org:2710/announce
	http://mgtracker.org:6969/announce
	http://open.touki.ru/announce.php

	//
	// Русский текстовый файл by Rusack (custom-made)
	//
	// // ignore line
	// # start of new category
	//


	# 000 Текст подсказок и уведомления экипажа
	Грузовой отсек корабля

	http://[2a04:ac00:1:3dd8::1:2710]:2710/announce

	http://0123456789nonexistent.com:80/announce

	http://0d.kebhana.mx:443/announce

	http://1337.abcvg.info:80/announce

	http://207.241.226.111:6969/announce

	# Repo: someuser/myframework
	# Fork: superteam/myframework

	# Track:
	git clone https://github.com/superteam/myframework.git
	cd myframework
	git remote add upstream https://github.com/someuser/myframework.git

	# Update:
	git fetch upstream

	# FORCE PORT 80 (insecure / regular traffic)
	RewriteEngine On
	RewriteCond %{HTTPS} on
	RewriteRule ^ http://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

	###########################################################

	#FORCE PORT 443 && REMOVE WWW. (secure / SSL)
	RewriteCond %{SERVER_PORT} 80
	RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R,L]