re-base on destinygg repo
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Investigate if we can rebase easily (is this possible on GitHub without losing stuff like issues and PRs?), since we shouldn't depend on the bbdgg repo. If anything they should depend on us.
Things like new animations we add also shouldn't be in the bbdgg.scss (or so), but added/moved to the "correct" place in the original repo.
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
Start by investigating GitHub options for rebasing or migrating the repository without losing issues and pull requests. Then inspect bbdgg.scss and the corresponding styles in the original repository. Done means chat-gui no longer depends on bbdgg and new animations are placed in the original repository's appropriate location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100