All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
Here we write upgrading notes for brands. It's a team effort to make them as
/********************** | |
* fordingTheRiver.js * | |
********************** | |
* | |
* And there's the river. Fortunately, I was prepared for this. | |
* See the raft on the other side? | |
* | |
* Everything is going according to plan. | |
*/ |
<?php | |
use Sabberworm\CSS\Parser; | |
use Sabberworm\CSS\RuleSet\DeclarationBlock; | |
$dom = new DOMDocument(); | |
$dom->loadHTML( | |
' | |
<!DOCTYPE html> | |
<html> |
#!/usr/bin/env bash | |
# Necessary to use the MIT keyserver on Ubuntu 20.04/Regolith 1.4 with gpg | |
gpg --keyserver hkp://pgp.mit.edu --recv-keys 3FEF9748469ADBE15DA7CA80AC2D62742012EA22 |
<?php | |
/** | |
* AMP Wordfence Compat plugin bootstrap. | |
* | |
* @package Google\AMP_Wordfence_Compat | |
* @author Weston Ruter, Google | |
* @license GPL-2.0-or-later | |
* @copyright 2020 Google Inc. | |
* | |
* @wordpress-plugin |
<?php | |
/** | |
* AMP Query Monitor Compat | |
* | |
* @package AMP_Query_Monitor_Compat | |
* @author Weston Ruter, Google | |
* @license GPL-2.0-or-later | |
* @copyright 2019 Google LLC | |
* | |
* @wordpress-plugin |
#!/bin/bash | |
# A bash script to update a Cloudflare DNS A record with the external IP of the source machine | |
# Used to provide DDNS service for my home | |
# Needs the DNS record pre-creating on Cloudflare | |
# Proxy - uncomment and provide details if using a proxy | |
#export https_proxy=http://<proxyuser>:<proxypassword>@<proxyip>:<proxyport> | |
# Cloudflare zone is the zone which holds the record |
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
Here we write upgrading notes for brands. It's a team effort to make them as
<!-- Start the link --> | |
<a href="http://cbc.ca/news"> | |
<!-- create button with id so we can target it with the CSS we're gonna use to make it float --> | |
<button id="safe-exit-button">Safe Exit</button> | |
<!-- Stop the link --> | |
</a> |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j