Closed matentzn closed 1 year ago
Nico, Thanks! I tried it in my fork and it works. I also made an edit on your fork (sorry about that), and because there was already a release it failed. So one thing to note is to only edit once per day. We don't update this file that much so one edit session per day is fine.
On Thu, Jun 8, 2023 at 8:00 AM Nico Matentzoglu @.***> wrote:
replaces #45 https://github.com/midas-network/midas-data/pull/45
You basically have to merge this @hoganwr https://github.com/hoganwr then go to the repo settings, and in the repos setting, allow actions to write information: [image: image] https://user-images.githubusercontent.com/7070631/244374680-5884a109-a7f3-4af6-b0c8-43a2e272505a.png
I don't know if the pipeline will run all by itself the moment you merge, lets see.
After that every time the edit file or an import changes, the release pipeline is triggered.
If you want to test it in a safer environment:
Use your fork!
You can view, comment on, or merge this pull request online at:
https://github.com/midas-network/midas-data/pull/46 Commit Summary
- ac15da8 https://github.com/midas-network/midas-data/pull/46/commits/ac15da8543be96cbcaf0e117b8d3dcae909bfa7a Load safe midas-data with Protege 561
- d6572b9 https://github.com/midas-network/midas-data/pull/46/commits/d6572b95b37ee73565480b6d45d9e169d071e817 First draft Make pipeline
- 272089c https://github.com/midas-network/midas-data/pull/46/commits/272089cd2b280f1636545d21240ce2db8e065ac3 Updated main release file
- b869eb4 https://github.com/midas-network/midas-data/pull/46/commits/b869eb4dbdffdcf365bc540fc14bbc31b486d774 Merge pull request #1 from matentzn/midas-makefile
- 3bc106c https://github.com/midas-network/midas-data/pull/46/commits/3bc106c9fd3f0c0c954079785ee0ed117ad630c7 Create release.yml
- 77ac773 https://github.com/midas-network/midas-data/pull/46/commits/77ac7732d8eee465aa96930542c05f05b5ca3269 Update release.yml
- 57dbce8 https://github.com/midas-network/midas-data/pull/46/commits/57dbce8e05bece9530458704de280eafb06d7980 Update release files
- 1c2daf7 https://github.com/midas-network/midas-data/pull/46/commits/1c2daf74cacf4cbde78729c0e4ebf7a1afdc1b85 Update release.yml
- 17be5ac https://github.com/midas-network/midas-data/pull/46/commits/17be5acc9bdd3272a684415e51426741821101d5 Merge branch 'main' of https://github.com/matentzn/midas-data
- 9172cf7 https://github.com/midas-network/midas-data/pull/46/commits/9172cf702823005c6f3cce28bbf923972ff25aac Update release files
- 8f3b5cf https://github.com/midas-network/midas-data/pull/46/commits/8f3b5cf533260833fc13cac1227892c62f02847e Update release.yml
- 78bec0e https://github.com/midas-network/midas-data/pull/46/commits/78bec0e74f73e32986c1c0edd9492ce9e3fa12ab Merge branch 'main' of https://github.com/matentzn/midas-data
- d2b0961 https://github.com/midas-network/midas-data/pull/46/commits/d2b0961059cd37a62a36c50c0640f0b62d07bcc8 Update release.yml
- 33d2757 https://github.com/midas-network/midas-data/pull/46/commits/33d275760a181c7bce55a1840ef56f2cfeb31b31 Update midas-data-edit.owl
- c22198a https://github.com/midas-network/midas-data/pull/46/commits/c22198ae67754c2b37fa4060bbef3e9038e4f831 Update release files
- e4e9434 https://github.com/midas-network/midas-data/pull/46/commits/e4e9434b059dbdb49b4eb2f96f35ade7896fda35 Update midas-data-edit.owl
- 834c85a https://github.com/midas-network/midas-data/pull/46/commits/834c85a58b64336f293bdba358957be20850ff62 Merge branch 'main' of https://github.com/matentzn/midas-data
- e7a1e0e https://github.com/midas-network/midas-data/pull/46/commits/e7a1e0e20d0aeacf756d4a0b5999a0250ae7c2e5 Update release files
File Changes
(9 files https://github.com/midas-network/midas-data/pull/46/files)
- A .github/workflows/release.yml https://github.com/midas-network/midas-data/pull/46/files#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34 (59)
- M .gitignore https://github.com/midas-network/midas-data/pull/46/files#diff-bc37d034bad564583790a46f19d807abfe519c5671395fd494d8cce506c42947 (4)
- M midas-data.owl https://github.com/midas-network/midas-data/pull/46/files#diff-c71e8bae5ce994ce45da5311c23ec3faf6dc14225c287e0d6222d8af92bfdca7 (314)
- A src/ontology/Makefile https://github.com/midas-network/midas-data/pull/46/files#diff-1376bbad1ef43bed6c9aed84b7d52471e63c87277b2b3f72ed0a5bdef481b638 (72)
- A src/ontology/catalog-v001.xml https://github.com/midas-network/midas-data/pull/46/files#diff-1767a95a5492cdd15ad99a4e14e9b8e9bf531f8758dba8cadb180951ccfe9e7e (5)
- A src/ontology/imports/apollo-sv_import.owl https://github.com/midas-network/midas-data/pull/46/files#diff-adc46e7c71c0330a7e84938ff6957985434f041608041b587ba3ac568d4a73d7 (416)
- A src/ontology/imports/seed.txt https://github.com/midas-network/midas-data/pull/46/files#diff-fff3fe0e77571b7067a41b52cd8beb80363f51f07b72041c6239c5fea52c3401 (22)
- A src/ontology/midas-data-edit.owl https://github.com/midas-network/midas-data/pull/46/files#diff-a295bcab45dc0233785ae3d95f47fd44aeed3eaf163bd3c2018cc7bcd371ccbb (1502)
- A src/ontology/midas-data.owl https://github.com/midas-network/midas-data/pull/46/files#diff-a43a947afefcfcbcc89bbb353fece0229a2385433fd68458b09e2c2e0b67c60f (1668)
Patch Links:
- https://github.com/midas-network/midas-data/pull/46.patch
- https://github.com/midas-network/midas-data/pull/46.diff
— Reply to this email directly, view it on GitHub https://github.com/midas-network/midas-data/pull/46, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJR55TRJROLF2P3KQDJTJ3XKG5G3ANCNFSM6AAAAAAY7GFMR4 . You are receiving this because you were mentioned.Message ID: @.***>
Exactly, this is the downside of this approach! If it turns out to be an issue, you can also simply reactive the automation and have it, instead, be triggered manually by the click of a two buttons (on https://github.com/midas-network/midas-data/actions, you would click on the workflow and on "Run Workflow"). I would try to see how you get on with the automated system for now!
Let me know what you need in terms of documentation, and where to put it for this repo.
I think just basic release workflow documentation, and the usual place: markdown files in src/docs? Does that sound ok?
Ok you can merge this here, I will provide documentation in a separate PR.
replaces #45
You basically have to merge this @hoganwr then go to the repo settings, and in the repos setting, allow actions to write information:
I don't know if the pipeline will run all by itself the moment you merge, lets see.
After that every time the edit file or an import changes, the release pipeline is triggered.
If you want to test it in a safer environment:
Use your fork!