Skip to content

Conversation

@rnro
Copy link
Collaborator

@rnro rnro commented Nov 6, 2024

Motivation:

  • Reduce duplication
  • Centralise boilerplate changes when new Swift versions are picked up.
  • Benefit from centralised work to add new linting / test infrastructure.

Modifications:

Changes of note:

  • Use soundness checks from swiftlang/github-workflows.
  • Retain bespoke license-checking code for .swift files as the gRPC header style is very different to most templates.

Result:

More test, linting, formatting coverage. More common CI with other Swift on Server projects.

@rnro rnro added the 🔨 semver/patch No public API change. label Nov 6, 2024
@@ -0,0 +1,37 @@
name: Soundness
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we inline this in pull_request.yml?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We can but then it won't display as PR / Soundness / Swift license headers check (pull_request) as the other soundness and license header checks do, that's the reason for the split-out.

Copy link
Collaborator

Choose a reason for hiding this comment

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

What would it display as?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think PR / Swift license headers check (pull_request)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I thought grouping the like-checks was nice. So that both license header checks appeared in the same part of the hierarchy and are grouped if you look at the Checks tab.

@rnro rnro force-pushed the adopt_standardized_github_actions branch 8 times, most recently from 8c94dde to f84c920 Compare November 6, 2024 15:32
@rnro rnro requested a review from glbrntt November 6, 2024 15:35
Copy link
Collaborator

@glbrntt glbrntt left a comment

Choose a reason for hiding this comment

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

One questions. Looks great though, thanks @rnro

Motivation:

* Reduce duplication
* Centralise boilerplate changes when new Swift versions are picked up.
* Benefit from centralised work to add new linting / test
  infrastructure.

Modifications:

Changes of note:
* Use soundness checks from swiftlang/github-workflows.
* Retain bespoke license-checking code for .swift files as the gRPC
  header style is very different to most templates.

Result:

More test, linting, formatting coverage. More common CI with other Swift
on Server projects.
@rnro rnro force-pushed the adopt_standardized_github_actions branch from 82e097e to bc39a3e Compare November 7, 2024 13:23
@glbrntt glbrntt merged commit 15556d9 into main Nov 7, 2024
27 of 29 checks passed
@glbrntt glbrntt deleted the adopt_standardized_github_actions branch November 7, 2024 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🔨 semver/patch No public API change.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants