Skip to content

Conversation

mateuszkwiecinski
Copy link
Contributor

Description

As discussed on Slack - I'm proposing a few changes to the build files. Each are in separate commit, I can drop any of them if they are not considered an improvement 😅

Checklist

Before submitting the PR, please check following (checks which are not relevant may be ignored):

  • Commit message are well written. In addition to a short title, the commit message also explain why a change is made.
  • At least one commit message contains a reference Closes #<xxx> or Fixes #<xxx> (replace<xxx> with issue number)
  • Tests are added
  • KtLint format has been applied on source code itself and violations are fixed
  • PR title is short and clear (it is used as description in the release changelog)
  • PR description added (background information)

Documentation is updated. See difference between snapshot and release documentation

  • Snapshot documentation in case documentation is to be released together with a code change
  • Release documentation in case documentation is related to a released version of ktlint and has to be published as soon as the change is merged to master

@mateuszkwiecinski mateuszkwiecinski marked this pull request as ready for review June 28, 2025 18:21
@paul-dingemans paul-dingemans merged commit 2dc1564 into pinterest:master Jun 29, 2025
10 checks passed
@mateuszkwiecinski mateuszkwiecinski deleted the build_improvements branch July 13, 2025 06:45
@paul-dingemans paul-dingemans changed the title A bunch of build changes Improve build Jul 14, 2025
@paul-dingemans paul-dingemans added this to the 1.7.0 milestone Jul 14, 2025
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