You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if: github.ref == 'refs/heads/main' # only create github release on main branch
61
44
id: create_release
62
45
uses: actions/create-release@v1
63
46
env:
@@ -71,12 +54,13 @@ jobs:
71
54
draft: false
72
55
prerelease: false
73
56
- name: Upload Release Asset
57
+
if: github.ref == 'refs/heads/main'
74
58
id: upload-release-asset
75
59
uses: actions/upload-release-asset@v1
76
60
env:
77
61
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
78
62
with:
79
63
upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
Repository for data related to Centrifuge Prime users.
3
+
Repository for data related to Centrifuge Prime users.
4
+
5
+
## Publishing to IPFS
6
+
7
+
### Dev
8
+
9
+
Opening a PR will trigger a deployment of the `dev-data.json` file to IPFS. The new hash can be found in the `Upload to IPFS` step in the [Publish action](https://github.com/centrifuge/prime-data/actions/workflows/publish_to_ipfs.yml).
10
+
11
+
### Prod
12
+
13
+
Merging PR to main will trigger a release of the `data.json` file to IPFS. The new hash can be found in the latest [Github release](https://github.com/centrifuge/prime-data/releases).
0 commit comments