changed-files
clang-format-lint-action
| changed-files | clang-format-lint-action | |
|---|---|---|
| 6 | 1 | |
| 1,521 | 129 | |
| 3.7% | - | |
| 9.8 | 6.7 | |
| 8 days ago | about 2 months ago | |
| TypeScript | Python | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
changed-files
-
Why it is Important to Update Linters and How to Do it Right
We need to add two additional steps. The first one is to retrieve all new files, and the second one is to run the enhanced config only on the new files. In this example the third-party GitHub Action called changed-files is used to obtain the new files. In the GitHub Marketplace for Actions, there is a considerable number of similar actions with similar functionality. You can choose the one that suits you best, as the functionality is more or less the same for all of them.
-
Attempting a larger bug fix II - Execution
I determined this after dozens of attempts working with the other GitHub Action, tj-actions/changed-files which feeds a list of modified files to clang-format-lint.
-
Yarn workspaces/monorepo and CI/CD
GitHub actions has actions that do similar, I’ve used this one before with great success: https://github.com/tj-actions/changed-files
-
Turborepo + GitHub Actions
You could also clean up your changed files job by using this (https://github.com/tj-actions/changed-files) or something similar. That would at least make it easier to understand what it's supposed to be doing. You can use it to get the directories containing any changed package.json files. Then use that output as as a matrix input.
- GitHub Actions Pitfalls
-
GitHub Action to run mypy on changed files only
View on GitHub
clang-format-lint-action
-
Attempting a larger bug fix II - Execution
Over the last couple of weeks, I deliberated on how to add my bugfix/feature upgrade to DoozyX/clang-format-lint. I've never worked on a GitHub Action before, and I wasn't sure how to test my changes, as this is a GitHub Action to be used within another GitHub Action. After a couple days, I consulted my class instructor for some advice.
What are some alternatives?
actionlint - :octocat: Static checker for GitHub Actions workflow files
skyrim-community-shaders - SKSE core plugin for community-driven advanced graphics modifications for AE, SE and VR. Also fixes bugs and improves performance.
Image-Optimizer-Action - A Github Action to optimize / compress images in your repository
cpp-linter-action - A Github Action for linting C/C++ code integrating clang-tidy and clang-format to collect feedback provided in the form of file-annotations, thread-comments, workflow step-summary, and Pull Request reviews.
paths-filter - Conditionally run actions based on files modified by PR, feature branch or pushed commits
github-action-utils - Collection of python functions that can be used to run GitHub Action Workflow Commands
runner-images - GitHub Actions runner images
Changelog CI - Changelog CI is a GitHub Action that enables a project to automatically generate changelogs
template.github.semver - Template for Projects that use Github Actions and Hooks to enforce Semantic Versioning
gh-action-pypi-publish - The blessed :octocat: GitHub Action, for publishing your :package: distribution files to PyPI: https://github.com/marketplace/actions/pypi-publish
ansible-lint-action - ❗️Replaced by https://github.com/marketplace/actions/run-ansible-lint
hello-github-actions - Create a GitHub Action and use it in a workflow.