ObolNetwork / ObolNetwork/obol-docs
Create github tag based release process
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- MDX
- Stars
- 27
- Forks
- 61
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Description
Problem to be Solved
Right now on the github site you can't see the docs sites versions, you can only see them in docusaurus/through the UI
Proposed Solution
Copy and modify the charon relase github action to publish a release for the obol docs site when a tag is pushed to main.
It should call yarn run version <TAG>. It should commit that content to main and push to the branch. This should trigger the normal re-deploy process.
In scope is replacing all of the old versions that are hardcoded into the text everywhere. Docusaurus probably have a templating approach to make
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.