Skip to content

Conversation

turt2live
Copy link
Member

This is what the lint.sh script does, so for people that can't run the script we can offer the same function via GHA.

Note: I have no way of testing this, and copy/pasted code from the lint (schema) action.

Pull Request Checklist

  • Pull request is based on the develop branch
  • Pull request includes a changelog file. The entry should:
    • Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from EventStore to EventWorkerStore.".
    • Use markdown where necessary, mostly for code blocks.
    • End with either a period (.) or an exclamation mark (!).
    • Start with a capital letter.
    • Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry.
  • Code style is correct (run the linters)

@turt2live turt2live requested a review from a team as a code owner June 19, 2025 17:40
@turt2live turt2live mentioned this pull request Jun 19, 2025
3 tasks
Copy link
Member

@anoadragon453 anoadragon453 left a comment

Choose a reason for hiding this comment

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

Perhaps instead we should just have this workflow run ./scripts-dev/lint.sh so it doesn't become out of sync again?

@turt2live
Copy link
Member Author

I'm not familiar enough with the script to confidently make that happen, but I'm also not attached to this PR (other than being the sole user of the action). If it makes more sense to do that, I'd +1 that change, but can't commit to making it happen, sorry.

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