Go to file
G 8eb2bef7f5
Update open problems (#91)
* vacdev(open problems): add Halo2 in browser

* feat(open problems): update applied zk

* address reviewers comments
2022-09-01 09:39:36 +02:00
.github Update labels.yml 2022-08-02 16:17:14 +08:00
_data/authors Staging (#67) 2022-06-10 13:52:01 +01:00
research edit(relay anonymity) 2022-07-22 17:52:06 +02:00
static-assets post: relay anonymity (#71) 2022-07-22 13:38:54 +08:00
.gitignore Staging (#67) 2022-06-10 13:52:01 +01:00
README.md Update staging (#83) 2022-07-29 15:40:32 +08:00
config.json Update copy (#85) 2022-08-05 14:42:11 +08:00
contribute.md contribute pseudonymously (#92) 2022-08-30 10:34:34 +02:00
media.md Feat/update copy (#79) 2022-08-02 12:32:48 +08:00
open-problems.md Update open problems (#91) 2022-09-01 09:39:36 +02:00
principles.md Update copy (#85) 2022-08-05 14:42:11 +08:00
projects.md Update copy (#85) 2022-08-05 14:42:11 +08:00
publications.md Update copy (#85) 2022-08-05 14:42:11 +08:00
research-areas.md Add/research areas roadmaps (#87) 2022-08-25 10:48:44 +02:00
vac.md Update copy (#85) 2022-08-05 14:42:11 +08:00

README.md

Vac.dev Website

Made and deployed with logos site-builder.

Continuous Deloyment

Change Process

  1. Create a new working branch from staging: git checkout staging; git checkout -b my-changes;
  2. Proceed with changes, push to origin and open a Pull Request against staging;
  3. Once approved, merge pull request, check changes on staging.vac.dev;
  4. Once ready to promote to live website, rebase master on staging: git checkout master; git pull master; git rebase origin/staging; git push.