README: Add community and open source related links (#109)

Adds community and open source links that are in other repos (e.g. base-org/node, base-org/pessimism).

Author: wbnns

README.md

@@ -1,43 +1,70 @@
+![Base](logo.webp)
+
 # contract-deployments
 
 This repo contains execution code and artifacts related to Base contract deployments, upgrades and calls. For actual contract implementations, see [base-org/contracts](https://github.com/base-org/contracts).
 
 This repo is structured with each network having a high level directory which contains sub directories of any "tasks" (contract deployments/calls) that have happened for that network.
 
+<!-- Badge row 1 - status -->
+
+[![GitHub contributors](https://img.shields.io/github/contributors/base-org/contract-deployments)](https://github.com/base-org/contract-deployments/graphs/contributors)
+[![GitHub commit activity](https://img.shields.io/github/commit-activity/w/base-org/contract-deployments)](https://github.com/base-org/contract-deployments/graphs/contributors)
+[![GitHub Stars](https://img.shields.io/github/stars/base-org/contract-deployments.svg)](https://github.com/base-org/contract-deployments/stargazers)
+![GitHub repo size](https://img.shields.io/github/repo-size/base-org/contract-deployments)
+[![GitHub](https://img.shields.io/github/license/base-org/contract-deployments?color=blue)](https://github.com/base-org/contract-deployments/blob/main/LICENSE)
+
+<!-- Badge row 2 - links and profiles -->
+
+[![Website base.org](https://img.shields.io/website-up-down-green-red/https/base.org.svg)](https://base.org)
+[![Blog](https://img.shields.io/badge/blog-up-green)](https://base.mirror.xyz/)
+[![Docs](https://img.shields.io/badge/docs-up-green)](https://docs.base.org/)
+[![Discord](https://img.shields.io/discord/1067165013397213286?label=discord)](https://base.org/discord)
+[![Twitter BuildOnBase](https://img.shields.io/twitter/follow/BuildOnBase?style=social)](https://twitter.com/BuildOnBase)
+
+<!-- Badge row 3 - detailed status -->
+
+[![GitHub pull requests by-label](https://img.shields.io/github/issues-pr-raw/base-org/contract-deployments)](https://github.com/base-org/contract-deployments/pulls)
+[![GitHub Issues](https://img.shields.io/github/issues-raw/base-org/contract-deployments.svg)](https://github.com/base-org/contract-deployments/issues)
+
 ## Setup
 
 First install forge if you don't have it already:
-* Run `make install-foundry` to install [`Foundry`](https://github.com/foundry-rs/foundry/commit/3b1129b5bc43ba22a9bcf4e4323c5a9df0023140).
+
+- Run `make install-foundry` to install [`Foundry`](https://github.com/foundry-rs/foundry/commit/3b1129b5bc43ba22a9bcf4e4323c5a9df0023140).
 
 To execute a new task run one of the following commands (depending on the type of change you're making):
-* For incident response commands: `make setup-incident network=<network> incident=<incident-name>`
-* For full new deployment (of L1 contracts related to Base): `make setup-deploy network=<network>`
-* For contract calls, upgrades, or one-off contract deployments: `make setup-task network=<network> task=<task-name>`
+
+- For incident response commands: `make setup-incident network=<network> incident=<incident-name>`
+- For full new deployment (of L1 contracts related to Base): `make setup-deploy network=<network>`
+- For contract calls, upgrades, or one-off contract deployments: `make setup-task network=<network> task=<task-name>`
 
 Next, `cd` into the directory that was created for you and follow the steps listed below for the relevant template.
 
 ## Directory structure
 
 Each task will have a directory structure similar to the following:
 
-* **[inputs/](/inputs)**  any input json files
-* **[records/](/records)** foundry will autogenerate files here from running commands
-* **[script/](/script)** place to store any one-off foundry scripts
-* **[src/](/src)** place to store any one-off smart contracts (long lived contracts should go in [base-org/contracts](https://github.com/base-org/contracts))
-* **.env** place to store env variables specific to this task
+- **[inputs/](/inputs)** any input json files
+- **[records/](/records)** foundry will autogenerate files here from running commands
+- **[script/](/script)** place to store any one-off foundry scripts
+- **[src/](/src)** place to store any one-off smart contracts (long lived contracts should go in [base-org/contracts](https://github.com/base-org/contracts))
+- **.env** place to store env variables specific to this task
 
 ## Using the incident response template
 
 This template contains scripts that will help us respond to incidents efficiently.
 
 To use template during an incident:
+
 1. Fill in TODOs in the relevant script.
 1. Fill in dependency commit values in the `.env` file.
 1. Delete the other scripts that are not being used so that you don't run into build issues.
 1. Check in code once addresses have been filled in.
 1. Have each signer pull the branch, and run relevant signing command from the Makefile.
 
 To add new incident response scripts:
+
 1. Any incident response related scripts should be included in this template (should be generic, not specific to network), with specific TODOs wherever addresses or other details need to be filled in.
 1. Add the relevant make commands that would need to be run for the script to the template Makefile
 1. Add relevant mainnet addresses in comments to increase efficiency responding to an incident.
@@ -46,19 +73,18 @@ To add new incident response scripts:
 
 This template is used for deploying the L1 contracts in the OP stack to set up a new network.
 
-1. Specify the commit of [Optimism code](https://github.com/ethereum-optimism/optimism) and [Base contracts code](https://github.com/base-org/contracts)  you intend to use in the `.env` file
+1. Specify the commit of [Optimism code](https://github.com/ethereum-optimism/optimism) and [Base contracts code](https://github.com/base-org/contracts) you intend to use in the `.env` file
 1. Run `make deps`
 1. Fill in the `inputs/deploy-config.json` and `inputs/misc-config.json` files with the input variables for the deployment.
 1. See the example `make deploy` command. Modifications may need to be made if you're using a key for deployment that you do not have the private key for (e.g. a hardware wallet)
 1. Run `make deploy` command
 1. Check in files to github. The files to ignore should already have been specified in the `.gitignore`, so you should be able to check in everything.
 
-
 ## Using the generic template
 
 This template can be used to do contract calls, upgrades or one-off deployments.
 
-1. Specify the commit of [Optimism code](https://github.com/ethereum-optimism/optimism) and [Base contracts code](https://github.com/base-org/contracts)  you intend to use in the `.env` file
+1. Specify the commit of [Optimism code](https://github.com/ethereum-optimism/optimism) and [Base contracts code](https://github.com/base-org/contracts) you intend to use in the `.env` file
 1. Run `make deps`
 1. Put scripts in the `scripts` directory (see examples that are part of the template, for example there is a file `TransferOwner.s.sol`, which can be used to setup the ownership transfer task). See note below if running a task that requires a multisig to sign.
 1. Call scripts from the Makefile (see examples in the template Makefile that's copied over).