bsnacks000

from sqlalchemy import create_engine
from sqlalchemy.orm import sessionmaker, scoped_session

from contextlib import contextmanager

import logging
l = logging.getLogger(__name__)


class DataAccessLayer(object):

ocefpaf

# See https://www.anaconda.com/understanding-and-improving-condas-performance/ for more info.

# help debug channel issues
show_channel_urls: true

# pip will always be installed with python 
add_pip_as_python_dependency: true

# strict priority and conda-forge at the top will ensure
# that all of your packages will be from conda-forge unless they only exist on defaults

bittner

Ctrl + Alt + Space

lisawolderiksen

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

fardjad

How to Install Homebrew on Manjaro

Steps

1. Install base-devel

    pacman -Syu # CAUTION: this updates the whole system
    pacman -S base-devel
   

2. Run the installer script

alexcasalboni

const zlib = require('zlib');

exports.decode = async (data) => {
    const compressedPayload = Buffer.from(data, 'base64');
    const jsonPayload = zlib.gunzipSync(compressedPayload).toString('utf8');
    return JSON.parse(jsonPayload);
}

elerch

---
AWSTemplateFormatVersion: '2010-09-09'
Description: Sample template that contains a Lambda function behind an API GW
Resources:
  # BEGIN: Should only need this in an empty API Gateway situation
  ApiGatewayCloudWatchLogsRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument:
        Version: '2012-10-17'

parmentf

Type	Emoji	code
feat	✨	:sparkles:
fix	🐛	:bug:
docs	📚	:books:
style	💎	:gem:
refactor	🔨	:hammer:
perf	🚀	:rocket:
test	🚨	:rotating_light:
build	📦	:package:

lisawolderiksen

Adding co-authors to Git commits

How do you share credit for a new or altered piece of code when one person commits the change in a pair programming or mob programming session? And when you have questions about a particular change, how can you see in Git who has been working on that change, besides the committer? You add co-autors to your commits. This gist contains information on how to do that, so that the Git commit message contains a list of co-authors, and all co-autors for a commit are automatically listed in GitHubs web UI.

GitHub has some info on specifying co-authors here. This is good info, pretty straightforward. The gist of it (pun intended) is to include at least one blank line and then a line for each co-author like so Co-authored-by: name <[email protected]> at the very end of your commit message.

GitHub's recipe tells you [how to find the right e-mail address to use](https:

jakebrinkmann

/CHANGELOG merge=union