digitaljhelms

Branching

Quick Legend

Description, Instructions, Notes

Instance	Branch

danpoltawski

Simplified behat for Tim Hunt.

Disclaimers:

• I'm hoping this will help you understand so you can help us improve our documentation.
• This is simplified version, i'm ignoring some details which are unimportant for discusing this.

What Behat requires.

kralo

<?php
/**
 * Example for howto to serve a csv file for download in Moodle using the /lib/csvlib.class.php
 * Very handy for exporting various data. This example demonstrates csv data export from within a moodle plugin
 * 
 * This file is public domain where applicable, 
 * else GNU LGPL
 */
require_once '../../config.php'; // to include $CFG, for example
require_once ($CFG->libdir . '/csvlib.class.php');

smonn

How to install git-flow in Windows

When it says "Run command", copy and paste the command part into a CLI, such as Powershell or the command prompt (make sure Git is in the path).

0. Make sure Git is installed.
1. From http://gnuwin32.sourceforge.net/packages/util-linux-ng.htm, download the binaries and dependencies zip-files.
2. Extract them and copy the contents of the bin-folders into your Git installation's bin folder, for example C:\Program Files (x86)\Git\bin. To find out where it is run where.exe git.
3. Set root directory to where you want to clone git-flow.
4. Run git clone --recursive git://github.com/nvie/gitflow.git

auremoser

This template is my ideal format for issues submitted to a github repository.

ricca509

// OSX

open -na Google\ Chrome --args --disable-web-security --user-data-dir="/tmp/chrome_dev"

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

sandeepgill

<?php

class MoodleValetDriver extends BasicValetDriver
{
    protected $isStyleUri = false;
    protected $baseUri = '';
    protected $moodleStaticScripts = [
        'styles.php',
        'javascript.php',
        'jquery.php',

apua

IEEE Standards Association: https://en.wikipedia.org/wiki/IEEE_Standards_Association

Software documentation: https://en.wikipedia.org/wiki/Software_documentation

IEEE 1058 - Software project management:

• https://en.wikipedia.org/wiki/Software_project_management
• https://cours.etsmtl.ca/log792/private/restreint/IEEE_1058_Project_Management_Plan.pdf

IEEE 828 - Software configuration management: https://en.wikipedia.org/wiki/Software_configuration_management

ChristopherA

Brew Bundle Brewfile Tips

Copyright & License

Unless otherwise noted (either in this file or in a file's copyright section) the contents of this gist are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.

Sponsor

If you more tips and advice like these, you can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! This gist is all about Homebrew, so if you like it you can support it by donating to them or becoming one of their Github Sponsors.