Commit 4e139e0e authored by totten's avatar totten
Browse files

More civi-git-table notes

parent 4c4ddd59
......@@ -76,16 +76,11 @@ releaser gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json --tag -f
releaser gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json --publish
```
You might want to spot-check a few URLs to ensure the tags were published, e.g.
* https://github.com/civicrm/civicrm-backdrop/tree/1.x-5.X.0
* https://github.com/civicrm/civicrm-core/tree/5.X.0
* https://github.com/civicrm/civicrm-drupal/tree/6.x-5.X.0
* https://github.com/civicrm/civicrm-drupal/tree/7.x-5.X.0
* https://github.com/civicrm/civicrm-drupal-8/tree/5.X.0
* https://github.com/civicrm/civicrm-joomla/tree/5.X.0
* https://github.com/civicrm/civicrm-packages/tree/5.X.0
* https://github.com/civicrm/civicrm-wordpress/tree/5.X.0
To ensure the various tags were published and match the branches, use `civi-git-table`, as in:
```
civi-git-table --fetch 5.2.0 5.2
```
## 5: Update `versions.json`
......
......@@ -84,7 +84,7 @@ releaser gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json --tag -f
releaser gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json --publish
```
To ensure the tags were published, use `civi-git-table`:
To ensure the various tags were published and match the branches, use `civi-git-table`, as in:
```
civi-git-table --fetch 5.16.0 5.16.1 5.16
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment