github-sponsors-readme-action
setup-python
github-sponsors-readme-action | setup-python | |
---|---|---|
3 | 11 | |
61 | 1,543 | |
- | 2.5% | |
7.9 | 6.7 | |
8 days ago | 23 days ago | |
TypeScript | 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.
github-sponsors-readme-action
-
Add your GitHub Sponsors to your project README with Actions
Some time ago I wrote a GitHub Action that would allow you to add your GitHub Sponsors to your project README. I've been using it for a while now and wanted to share how you can also use it to add value to your sponsorship tiers. If you want to skip this and just go straight to the documentation click here.
-
Let's give recognition to those supporting our work on GitHub Sponsors.
JamesIves/github-sponsors-readme-action
-
Deploying to GitHub Pages using GitHub Actions
If you'd like to check out some of my other projects you can check out the Fetch API Data Action which I wrote an [article about (https://jamesiv.es/blog/github/actions/2020/03/07/fetching-authenticated-api-data/) a while ago or you can check out this one which I created to simplify the process of adding GitHub Sponsors to the README of popular projects as a perk for donating.
setup-python
-
CI/CI deploy a static website to AWS S3 bucket through Github Actions
Run a local host with the static website content with Python setup Github Actions
-
Disable Annotations in Github Actions
setup-python
-
Building project docs for GitHub Pages
The first two steps are setting up the job's environment. The checkout action will checkout out the repository at the triggering ref. The setup-python action will setup the desired Python runtime. My package supports Python 3.9+ so I'm targeting the minimum version for my build environments.
-
Gotchas when building GitHub self-hosted runners with AWS official AMIs/container images for Python apps
actions/setup-python@v4 does not support arm64 (https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json). See related Open issue https://github.com/actions/setup-python/issues/108.
-
Top 10 GitHub Actions You Should Use to set up your CI/CD Pipeline
The most popular ones are Node.js, Python, Java JDK, Go, .Net Core SDK.
-
Deploy Azure Static Web Apps using Python
To build your environment in GH Actions you'll need to add a block to your yaml file BEFORE the Azure Build and Deploy section. You'll need to include the setup-python action and specify the python version you would like to use. Use the major version of your python version so 3.10 and NOT 3.10.5. For more information and options on this you can check out the Setup-Python GH actions repo.
-
Deploying to GitHub Pages using GitHub Actions
Next up we'll need to add a step to compile our production ready build. For this we can add two new steps, one which configures our Node version to ensure it matches our application, followed by another that runs the necessary commands with npm. Depending on how your application is built you may need to add another step between these to install any sort of required environments such as Python or Java.
-
Air Quality - Pollutant Index - India
Python 3.9 is setup using actions/[email protected] and the pip packages are cached
-
Prefect CLI Action
It requires that the checkout and setup-python actions be used first.
-
Python CI/CD with GitHub Actions
First, we have to checkout the repository in GitHub Actions using GitHub's own checkout action. Then, we have to set up the Python version using GitHub's setup-python action. Finally, we can use Black's provided GitHub Action for checking formatting - it runs black --check --diff on the workflow runner's clone of the repo and outputs an error code if any Python file in the repo fails Black's formatting rules. Note that Black fails if the AST cannot be parsed (i.e. if there are any syntax errors), so it can also be used for checking syntax correctness, which itself is a good proxy for checking for merge conflict strings.
What are some alternatives?
fetch-api-data-action - 🚚 GitHub action for handling authenticated API requests, allowing you to save the data from the request into your workspace as an environment variable and a .json file.
checkout - Action for checking out a repo
sponsorkit - 💖 Toolkit for generating sponsors images 😄
cache - Cache dependencies and build outputs in GitHub Actions
github-pages-deploy-action - 🚀 Automatically deploy your project to GitHub Pages using GitHub Actions. This action can be configured to push your production-ready code into any branch you'd like.
virtual-environments - GitHub Actions runner images [Moved to: https://github.com/actions/runner-images]
Jenkins - Jenkins automation server
pyenv - Simple Python version management
ghsvg - GitHub Sponsors SVG
black - The uncompromising Python code formatter
setup-java - Set up your GitHub Actions workflow with a specific version of Java
upload-pages-artifact - A composite action for packaging and uploading an artifact that can be deployed to GitHub Pages.