TODOs to complete repo migration
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 3
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
- version 0.1.0 and setup bump2version
- move this repo to ome
- setup snoopycrimecop to merge PRs into merge-ci branch...
- setup snoopycrimecop omero-figure to consume that scc/figure merge-ci as submodule!
Not planned now (focus on browser PDF generation instead of python install & test etc):
- pypi and github actions to publish releases - Needs ome-figure on Pypi
- GitHub actions to test on PRs:
- JavaScript tests? (new)
- figure_export install and test
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 or tests are named. Start with the migration checklist in this issue and review the repository's current merge and submodule setup; done means snoopycrimecop merges PRs into merge-ci and omero-figure consumes that branch as a submodule. Publishing releases and PR test actions are explicitly out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100