Auto upstream update?

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
java
Domain
build-system

Research direction

No files, tests, or entry points are identified in the issue. Start by examining how Folia currently incorporates upstream Paper, Spigot, or CraftBukkit changes and how compile or patch failures are handled. Done means defining and implementing an automatic update path that proceeds only when upstream changes apply cleanly.

Written by the indexing model from the issue text.

Description

status: needs triage type: feature
Is your feature request related to a problem?

Folia doesn't get paper updates very much, maybe once a month or every 2 months

Describe the solution you'd like.

Have auto paper bump aslong as there aren't compile/patch issues, similar to how paper used to auto update from spigot/craftbukkit

Describe alternatives you've considered.

IDK

Other

No response

Dominant language
Shell
Stars
4.7k
Forks
651
Avg merge
10d 3h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 PaperMC/Folia

All issues in PaperMC/Folia

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.