- create tasks T{NNNN} asign them
- create a branch with name like "T{NNNN}-boo-hoo"
git checkout -b T1234-boo-foo
- commit changes on that branch until it gets ready to be reviewed
git commit -am 'first'
git commit -am 'now it works'
- check if it's lint free (NOTE: it runs lint against only modified files)
arc lint
- push a review request to the server. This will create a diff with id D{NNNN}
arc diff
const fs = require("fs"); | |
const moment = require("moment"); | |
const _ = require("lodash"); | |
const path = require("path"); | |
const agent = require("superagent-promise")(require("superagent"), Promise); | |
//Lang Codes https://ctrlq.org/code/19899-google-translate-languages | |
const YANDEX_API_KEYS = process.env.TRANSLATION_API_KEY; | |
const inputFile = "./data/en.json"; |
This is for an ISO UK layout:
Wiki: https://www.reddit.com/r/MechanicalKeyboards/wiki/pok3r Manual: http://www.vortexgear.tw/db/upload/webdata4/6vortex_20166523361966663.pdf
USB ID (from lsusb): Bus 020 Device 012: ID 04d9:0141 Holtek Semiconductor, Inc. USB Keyboard
If you use atom... download & install the following packages:
git config --global alias.st "status -s -b" | |
git config --global alias.di "diff" | |
git config --global alias.co "checkout" | |
git config --global alias.ci "commit" | |
git config --global alias.br "branch" | |
git config --global alias.l "log --online --decorate --graph" | |
git config --global alias.fixup "commit --amend -C HEAD" | |
git config --global alias.timeline "log --graph --branches --pretty=online --decorate" | |
git config --global alias.untracked-files "ls-files -o --exclude-standard" | |
git config --global alias.ignored-files "ls-files --others -i --exclude-standard" |
# http://itsecmedia.com/blog/post/2016/python-send-outlook-email/ | |
import win32com.client | |
from win32com.client import Dispatch, constants | |
const=win32com.client.constants | |
olMailItem = 0x0 | |
obj = win32com.client.Dispatch("Outlook.Application") | |
newMail = obj.CreateItem(olMailItem) | |
newMail.Subject = "I AM SUBJECT!!" |
FWIW: I didn't produce the content present here. I've just copy-pasted it from somewhere over the Internet, but I cannot remember exactly the original source. I was also not able to find the author's name, so I cannot give him/her the proper credit.
- By Edmond Lau
- Highly Recommended 👍
- http://www.theeffectiveengineer.com/
- http://stackoverflow.com/questions/804115 (
rebase
vsmerge
). - https://www.atlassian.com/git/tutorials/merging-vs-rebasing (
rebase
vsmerge
) - https://www.atlassian.com/git/tutorials/undoing-changes/ (
reset
vscheckout
vsrevert
) - http://stackoverflow.com/questions/2221658 (HEAD^ vs HEAD~) (See
git rev-parse
) - http://stackoverflow.com/questions/292357 (
pull
vsfetch
) - http://stackoverflow.com/questions/39651 (
stash
vsbranch
) - http://stackoverflow.com/questions/8358035 (
reset
vscheckout
vsrevert
)
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