Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Move the `upstream-rebuild` branch to `main`

Open
#216 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
wasm
Domain
tooling

Research direction

Review the repository's branch settings and the testsuite repository's branch expectations before changing anything. The work is complete when upstream-rebuild is the repository's main branch, the previous main history remains available under an agreed name, and downstream consumers resolve the intended branch.

Written by the indexing model from the issue text.

Description

This was discussed a bit during the CG meeting yesterday but I wanted to open an issue for this as well. Downstream consumers such as the testsuite repository pick up changes to tests from the main branch, and additionally when visiting the repository it's useful to see the current state on the landing page, currently the main branch as well.

If I might offer a concrete suggestion, it might be useful to rename main to old-main (please bikeshed) and then rename the upstream-rebuild branch to main to avoid losing histories.

Dominant language
WebAssembly
Stars
767
Forks
54
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WebAssembly/threads

All issues in WebAssembly/threads

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.