OneLiteFeatherNET / OneLiteFeatherNET/Voyager
chore: remove stale long-lived branches violating trunk-based workflow
Open
Beginner friendly
Nobody has claimed this yet.
chore
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 12
Description
The following remote branches violate the trunk-based development policy (only short-lived feature branches allowed). They should be deleted after confirming no unmerged work remains.
Branches to delete:
- `origin/develop`
- `origin/alpha`
- `origin/main-bak`
- `origin/main-bak2`
- `origin/master-bak`
- `origin/feature/rework`
- `origin/feature/spline-correction`
- `origin/feature/to-java`
- `origin/feat/minestom-migration-planning`
Acceptance criteria:
- All listed branches deleted from remote
- No unmerged commits lost (verify with `git log`)
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 listed remote branches with git log to verify that no unmerged commits would be lost. Delete only the named branches after that check, then confirm they no longer exist on the remote. Done means all listed branches are removed and the repository retains all unmerged work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devops, tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 70/100