Go to file
Daniel Kaiser 6802667182
list new deploy process in README (#76)
* list new deploy process in README

* Update README.md

Co-authored-by: ksr <kaiserd@users.noreply.github.com>
2022-07-26 16:22:18 +08:00
.github/workflows Staging (#67) 2022-06-10 13:52:01 +01:00
_data/authors Staging (#67) 2022-06-10 13:52:01 +01:00
about 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 list new deploy process in README (#76) 2022-07-26 16:22:18 +08:00
config.json Staging (#67) 2022-06-10 13:52:01 +01:00
projects.md Staging (#67) 2022-06-10 13:52:01 +01:00
research-areas.md Staging (#67) 2022-06-10 13:52:01 +01:00
vac.md Staging (#67) 2022-06-10 13:52:01 +01: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.