NEARBuilders / NEARBuilders/everything-dev
everything-dev: build, publish, stage, deploy
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 6
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
build - update Zephyr
publish - to KV
deploy - build, publish, re-trigger railway (alchemy https://github.com/alchemy-run/alchemy-effect)
stage - deploy but with staging
Permissions handled by near account auth
Contributor guide
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.
Research direction
Start by mapping the existing TypeScript runtime and the build, publish, stage, and deploy entry points; the issue names Zephyr, KV, Railway, Alchemy Effect, and Near account auth but no files or tests. Clarify the expected workflow and permissions, then verify that build, publish, deployment retriggering, and staging each work as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100