changed-files
combine-prs-workflow
Our great sponsors
changed-files | combine-prs-workflow | |
---|---|---|
6 | 3 | |
1,507 | 288 | |
6.0% | 0.3% | |
9.8 | 2.1 | |
6 days ago | 9 months ago | |
TypeScript | ||
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
combine-prs-workflow
-
Keeping dependencies in your GitHub projects up-to-date with Dependabot
To address inefficiency caused by separate PRs, a workflow was designed to join them automatically into one big PR. However, it was unable to deal with lockfile conflicts. PRs that caused conflict in the Combine PRs job, were omitted and you had to add them manually anyway. It spared some time, but the developer experience was still far from being perfect.
-
GitHub Actions Pitfalls
Another pitfall I ran into recently with a workflow I've been working on [1]: Checks and CI that are made with GitHub Actions are reported to the new Checks API, while some (all?) external services report to their old Statuses API. This makes it needlessly difficult to ascertain whether a PR/branch is "green" or not. They finally decided to create a "statusRollUp" that combines the state of the two APIs, but it's not available in their REST api, only their GraphQL API.
[1] https://github.com/hrvey/combine-prs-workflow/
-
Awesome GitHub Actions
GitHub Actions can do some neat things. I got tired of waiting for Dependabot (tool that makes automatic PRs to update your middleware, acquired by GitHub) to add an option to group PRs together (it opens a separate PR for each dependency that can be updated, so merging and re-running CI can take a long time) so I scratched my own itch and made a workflow that merges their PRs together: https://github.com/hrvey/combine-prs-workflow Been running it for a year now, and still pretty happy with it.
What are some alternatives?
actionlint - :octocat: Static checker for GitHub Actions workflow files
runner-images - GitHub Actions runner images
paths-filter - Conditionally run actions based on files modified by PR, feature branch or pushed commits
Image-Optimizer-Action - A Github Action to optimize / compress images in your repository
vitemadose - Détection de créneaux de vaccination disponibles pour l'outil ViteMaDose
gh-valet - Valet helps facilitate the migration of Azure DevOps, CircleCI, GitLab CI, Jenkins, and Travis CI pipelines to GitHub Actions.
template.github.semver - Template for Projects that use Github Actions and Hooks to enforce Semantic Versioning
ansible-lint-action - ❗️Replaced by https://github.com/marketplace/actions/run-ansible-lint
travis-yml - Travis CI build config processing