| Hey, I'm fryorcraken-110212804 and I have contributed to the RLN Trusted Setup Ceremony MPC Phase2 Trusted Setup ceremony. | |
| The following are my contribution signatures: | |
| Circuit # 1 (rln-withdraw) | |
| Contributor # 24 | |
| Contribution Hash: 5563e4f1 f92bbf7e 49678389 53a78088 | |
| 6f82e8ff 41b10abf d34ac2af cb028028 | |
| a1403999 229a3a32 ed06766f 5b91585f | |
| 6f47cbe1 e99781a2 4cd2be67 cd788ff2 |
As we are on-boarding more developers on js-waku, I wanted to share some thoughts around Pull Request management.
js-waku uses a GitHub Flow strategy:
master from which releases happen and is always ready (do not break master)master to isolate their work, the branch name must be descriptive (e.g. feat/name-of-feature).
| <!DOCTYPE html> | |
| <html lang='en'> | |
| <head> | |
| <meta charset='UTF-8'/> | |
| <meta content='width=device-width, initial-scale=1.0' name='viewport'/> | |
| <title>JS-Waku store script tag example</title> | |
| </head> | |
| <body> |
| <!DOCTYPE html> | |
| <html lang='en'> | |
| <head> | |
| <meta charset='UTF-8'/> | |
| <meta content='width=device-width, initial-scale=1.0' name='viewport'/> | |
| <title>JS-Waku Chat</title> | |
| </head> | |
| <body> |