Skip to content

fix: run lint in all circumstances #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 1, 2025
Merged

Conversation

SamMorrowDrums
Copy link
Collaborator

We need to run the linter in all circumstances, otherwise it cannot be a required check.

We need to run the linter in all circumstances, otherwise it cannot be a required check.
@SamMorrowDrums SamMorrowDrums requested review from Copilot and toby and removed request for Copilot April 1, 2025 22:18
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR removes file-specific path filtering from the lint workflow trigger so that the linter will run on every push or pull_request regardless of the modified file.

  • Removed file path restrictions in the push and pull_request triggers
  • Ensures linter runs in all circumstances as required

Tip: Copilot code review supports C#, Go, Java, JavaScript, Markdown, Python, Ruby and TypeScript, with more languages coming soon. Learn more

@SamMorrowDrums SamMorrowDrums merged commit b3a3d15 into main Apr 1, 2025
16 checks passed
manian0430 pushed a commit to ChrisLally/github-mcp-server that referenced this pull request Apr 12, 2025
We need to run the linter in all circumstances, otherwise it cannot be a required check.
@toby toby deleted the fix-linter-job branch April 21, 2025 16:21
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