Skip to content

Conversation

@Pankraz76
Copy link
Contributor

Please DO NOT FORCE PUSH. Don't worry about messy history, it's easier to do code review if we can tell what happened after the review, and force pushing breaks that.

Please make sure that your PR allows edits from maintainers. Sometimes it's faster for us to just fix something than it is to describe how to fix it.

Allow edits from maintainers

After creating the PR, please add a commit that adds a bullet-point under the [Unreleased] section of CHANGES.md, plugin-gradle/CHANGES.md, and plugin-maven/CHANGES.md which includes:

  • a summary of the change
  • either
    • a link to the issue you are resolving (for small changes)
    • a link to the PR you just created (for big changes likely to have discussion)

If your change only affects a build plugin, and not the lib, then you only need to update the plugin-foo/CHANGES.md for that plugin.

If your change affects lib in an end-user-visible way (fixing a bug, updating a version) then you need to update CHANGES.md for both the lib and all build plugins. Users of a build plugin shouldn't have to refer to lib to see changes that affect them.

This makes it easier for the maintainers to quickly release your changes :)

@Pankraz76 Pankraz76 force-pushed the pr-fix-GradleBestPractices branch from 13c3627 to b4b05d4 Compare November 19, 2025 10:39
@Pankraz76 Pankraz76 marked this pull request as ready for review November 19, 2025 10:39
@Pankraz76 Pankraz76 force-pushed the pr-fix-GradleBestPractices branch from b4b05d4 to 1f3bd8c Compare November 19, 2025 14:03
Copy link
Member

@nedtwigg nedtwigg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

needs merge conflict resolution

Signed-off-by: Vincent Potucek <vpotucek@me.com>
@Pankraz76 Pankraz76 force-pushed the pr-fix-GradleBestPractices branch from 1f3bd8c to 69d7d17 Compare November 20, 2025 11:59
Signed-off-by: Vincent Potucek <vpotucek@me.com>
}

repositories {
mavenCentral()
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i know spot needs this also rewrite.

Is it working without, why so?

Actually would expect mavenCentral to be kind of default best practice active by default following convention principle.

@Pankraz76
Copy link
Contributor Author

Pankraz76 commented Nov 20, 2025

please if consider merge, consider squash merge or i will do if you like history kind of obsolete on this.

@Pankraz76 Pankraz76 requested a review from nedtwigg November 20, 2025 12:19
@nedtwigg nedtwigg merged commit ed43dc2 into diffplug:main Nov 20, 2025
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants