lbryio / lbryio/block-explorer
CI / CD processes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Need a CI/CD solution for block-explorer. Currently, need to deploy changes manually.
## Internal Use
### Acceptance Criteria
1.
2.
3.
### Definition of Done
- [ ] Tested against acceptance criteria
- [ ] Tested against the assumptions of the user story
- [ ] The project builds without errors
- [ ] Unit tests are written and passing
- [ ] Tests on devices/browsers listed in the issue have passed
- [ ] QA performed & issues resolved
- [ ] Refactoring completed
- [ ] Any configuration or build changes documented
- [ ] Documentation updated
- [ ] Peer Code Review performed
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.
Research direction
No files, tests, or deployment entry points are named. Start by reviewing how the block-explorer is currently built and deployed manually, then define a CI/CD workflow that builds the project, runs its unit tests, and deploys changes; document the configuration and verify the acceptance criteria once they are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100