Migrate canonical repo from BitBucket to GitHub
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- git, github
- Domain
- infrastructure, release
Research direction
Start with the GitHub import feature and the existing yaml/libyaml repository, then review the listed branch and tag migration steps. Done means the Mercurial history is imported into GitHub, old tags are removed, old branches are renamed under old/, and the imported branches and tags are pushed to the canonical repository.
Written by the indexing model from the issue text.
Description
@sigmavirus24 and @ingydotnet are taking over maintenance of libyaml from @xitology.
The first step is to migrate the Mercurial repos on BitBucket to Git repos on GitHub. We hope this will make for a truly collaborative community maintenance environment.
Here are the steps being taken:
- Use GitHub import feature to migrate the repo into a temporary repo.
- Delete the old tags from https://github.com/yaml/libyaml
- Rename old branches in https://github.com/yaml/libyaml to
old/$name - Fetch all branches and tags from newly imported repo into https://github.com/yaml/libyaml
- Push all new branches and tags to https://github.com/yaml/libyaml
After this we will:
- Review the existing issues and pull requests
- Make new issues for all planned work
- Announce the changes to yaml-core@lists.sourceforge.net
- Announce changes in blog post on http://yaml.io
- Reach out to packagers: Debian et al
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 370
- PR merge metrics
- No merged PRs in 30d
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.
More from yaml/libyaml
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 Under an hour Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Similar issues
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·
-
bug Self Built Image SNAPSHOT Supported Device target/ramips
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100