Say what is expected of a pull request, and drop the develop download - #3161
Merged
Conversation
Contributions increasingly arrive written by AI tooling, which is fine in itself, but a growing share of them are opened unread: whole-tree reformats around a five-line change, patches the author cannot explain, review replies that are themselves generated. State the three things that make a pull request reviewable - read the diff, run it on a ruTorrent you actually use, answer reviews yourself - and that master is the branch to target. The download section still offered a develop tarball. That branch is retired; master is where work lands and a release is a tag on it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contributions increasingly arrive written by AI tooling, which is fine in itself, but a growing share of them are opened unread: whole-tree reformats around a five-line change, patches the author cannot explain, review replies that are themselves generated. State the three things that make a pull request reviewable - read the diff, run it on a ruTorrent you actually use, answer reviews yourself - and that master is the branch to target.
The download section still offered a develop tarball. That branch is retired; master is where work lands and a release is a tag on it.