changed-files
gh-action-pypi-publish
Our great sponsors
changed-files | gh-action-pypi-publish | |
---|---|---|
6 | 5 | |
1,507 | 834 | |
6.0% | 3.5% | |
9.8 | 8.3 | |
5 days ago | 11 days ago | |
TypeScript | Python | |
MIT License | BSD 3-clause "New" or "Revised" 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
gh-action-pypi-publish
-
PyPI new user and new project registrations temporarily suspended
> Recently I've seen someone on Reddit trying to automate the creation of PyPI projects through GitHub Actions. The person was complaining that the first deployment couldn't use an API key for that project since it didn't exist. So I'm not surprised some people are trying to do the same for malicious purposes.
Sorry for the tangent, but: you can do this now! If you use trusted publishing, you can register a "pending publisher" for a project that doesn't exist yet. When the trusted publisher (like GitHub Actions) is used, it'll create the project[1].
All of this is supported transparently by the official publishing action for GitHub Actions[2].
[1]: https://docs.pypi.org/trusted-publishers/creating-a-project-...
[2]: https://github.com/pypa/gh-action-pypi-publish
-
Publishing to PyPI via GitHub Action
In the documentation example, I see that the action yaml file contains the line uses: pypa/gh-action-pypi-publish@release/v1. I have never done this before and almost went with that, but I am not sure why the example shows v1 hardcoded, so I don't think I actually want this to happen. It doesn't seem to be well explained though, and the pypi-publish action repo was also quiet on this. Is this saying that it will create a release branch in my repo and call the release v1? Or how will this appear after I've done it? Will I have to manually change this v1 to v0.1.1 in the actions file AND the pyproject.toml?
-
"Even with --dry-run pip will execute arbitrary code found in the package's setup.py. In fact, merely asking pip to download a package can execute arbitrary code"
Yeah, you're uploading to PyPi in your pipeline, great. The custom github action still uses twine because the stdlib falls short on BASIC security. https://github.com/pypa/gh-action-pypi-publish/blob/unstable/v1/twine-upload.sh
-
Do you publish pypi source code to Github as well in the same form?
I never bothered with pypi myself but I hope the nudge into github actions helps you. I've found the following promising github action: https://github.com/pypa/gh-action-pypi-publish
- The Python Package Index is now a GitHub secret scanning integrator
What are some alternatives?
actionlint - :octocat: Static checker for GitHub Actions workflow files
build - A simple, correct Python build frontend
paths-filter - Conditionally run actions based on files modified by PR, feature branch or pushed commits
git-filter-repo - Quickly rewrite git repository history (filter-branch replacement)
runner-images - GitHub Actions runner images
git-repo-sync - Git Repo Sync enables you to synchronize code to other code management platforms, such as GitLab, Gitee, etc.
Image-Optimizer-Action - A Github Action to optimize / compress images in your repository
amplify-preview-actions - This action deploys your AWS Amplify pull request preview for your public repository
template.github.semver - Template for Projects that use Github Actions and Hooks to enforce Semantic Versioning
trufflehog - Find and verify credentials
ansible-lint-action - ❗️Replaced by https://github.com/marketplace/actions/run-ansible-lint
release - Contains every things needed to release jenkins core from the jenkins infra project