WebAssembly / WebAssembly/spec
Time to delete the old `master` branches?
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 3.5k
- Forks
- 539
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 13
Description
The spec repo (and it seems all the of forks) have a master branch which IIUC automatically tracks main. There was recently a change that disappeared because it was merged in the master instead of main: https://github.com/WebAssembly/memory64/pull/60#issuecomment-2168642148
Does anyone still rely on these master branch names? Can we remove them at this point? I assume they were intended only to exist for some transitional period.
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 checking the spec repository and its forks to confirm whether master still tracks main and whether any documented workflow or automation relies on it. The work is done when the dependency on master is understood and, if no reliance remains, the obsolete branch names are removed without affecting main.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100