margelo / margelo/react-native-nitro-sqlite
History loss upon migration
Open
Nobody has claimed this yet.
triage:needs-expert
- Dominant language
- C
- Stars
- 565
- Forks
- 53
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 18
Description
Hello, thank you for taking ownership of the library. I’m wondering if you could fork the opsfranco repo and maintain history.
Maintaining history has a lot of benefits and it’s what allowed me to contribute a minor fix to the opsfranco repo.
Thanks for considering it.
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 reviewing the request to fork the opsfranco repository and preserve its history in the current GitHub project. Done means the repository migration retains the prior project history; the issue names no source files, tests, or implementation entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100