-
Notifications
You must be signed in to change notification settings - Fork 33
Update go.mod on new go-ipfs release tags #45
Conversation
Thank you for submitting this PR!
Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution. |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
2 similar comments
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Diff of http-api-docs output: |
Address automation of HTTP API docs from ipfs/ipfs-docs#267.
The approach is to have http-api-docs repo monitor go-ipfs for new tags.
When a new tag is detected, http-api-docs bumps its go-ipfs dependency and submits a PR.
(We should probably automate the merging of the PR as well and tagging using the go-ipfs dependency tag.)
The idea is that, ipfs-docs will do the same, but it will monitor http-api-docs for new tags.
When a change occurs, it will build and use htpp-api-docs to update itself.
cc @lidel @aschmahmann