For educational reasons I've decided to create my own CA. Here is what I learned.
Lets get some context first.
| [alias] | |
| l = log --pretty=format:\"%C(yellow)%h%Cred%d\\ %Creset%s%Cblue\\ [%cn]\" --decorate | |
| g = log --oneline --decorate --graph | |
| s = status -sb | |
| co = checkout | |
| b = branch -avv | |
| ll = log --pretty=format:\"%C(yellow)%h%Cred%d\\ %Creset%s%Cblue\\ [%cn]\" --decorate --numstat | |
| lds = log --pretty=format:\"%C(yellow)%h\\ %ad%Cred%d\\ %Creset%s%Cblue\\ [%cn]\" --decorate --date=short | |
| ld = log --pretty=format:\"%C(yellow)%h\\ %ad%Cred%d\\ %Creset%s%Cblue\\ [%cn]\" --decorate --date=relative | |
| lc = log master.. |
| # Create the datadog user with select only permissions: | |
| # CREATE USER datadog WITH PASSWORD '<complex_password>'; | |
| # | |
| # Grant select permissions on a table or view that you want to monitor: | |
| # GRANT SELECT ON <schema>.<table> TO datadog; | |
| # | |
| # Grant permissions for a specific column on a table or view that you want to monitor: | |
| # GRANT SELECT (id, name) ON <schema>.<table> TO datadog; | |
| # | |
| # Let non-superusers look at pg_stat_activity in a read-only fashon. |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git@github.com:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this: