Content
Milestone OP-14179: Legal documents in opf/legal are up-to-date in repo and downstream (DPA in saas)
View differences
Updated by Christophe Bliard over 2 years ago
**0: Make sure the legal docs are up-to-date in the legal repo itself (assign to Niels)**
**1: Check out the latest legal repository**
```bash
git clone git@github.com:opf/legal.git
```
If you have it already, update it.
```bash
git fetch origin
```
**2: Update the legal files in** `saas-openproject`
You need to have cloned the [saas-openproject repository](https://github.com/opf/saas-openproject) and [linked it to a core repository](https://github.com/opf/saas-openproject/blob/dev/bin/setup).
The commands below assume that the linked core repository is located in a `core/` directory inside saas-openproject.
```bash
export BASE_URL=file://<path-to-legal-repo-from-above>
cd saas-openproject
git checkout release/13.0 # insert current release here
cd core
git checkout release/13.0 # insert current release here
bundle install
bundle exec rake subscriptions:dpa:update
cd ..
```
Commit and push the changes from saas-openproject repository if there are any.
**1: Check out the latest legal repository**
```bash
git clone git@github.com:opf/legal.git
```
If you have it already, update it.
```bash
git fetch origin
```
**2: Update the legal files in** `saas-openproject`
You need to have cloned the [saas-openproject repository](https://github.com/opf/saas-openproject) and [linked it to a core repository](https://github.com/opf/saas-openproject/blob/dev/bin/setup).
The commands below assume that the linked core repository is located in a `core/` directory inside saas-openproject.
```bash
export BASE_URL=file://<path-to-legal-repo-from-above>
cd saas-openproject
git checkout release/13.0 # insert current release here
cd core
git checkout release/13.0 # insert current release here
bundle install
bundle exec rake subscriptions:dpa:update
cd ..
```
Commit and push the changes from saas-openproject repository if there are any.