The main branch is used for testing the actions.
Branches starting with dev/ are either wip or experiments.
Build wheels for pip libraries that require being built from source.
uses: melMass/actions@build-python-wheels
with:
wheels: "numpy,scipy" # Required: comma separated list of wheels to build
python-version: "3.10" # Optional: defaults to 3.10
requirements-file: "requirements.txt" # Optional
dependencies: "wheel setuptools" # Optional: additional dependencies to installPackages a Python environment with its dependencies for later use.
uses: melMass/actions@package-python
with:
python-version: "3.10" # Optional: defaults to 3.10
requirements-file: "requirements.txt" # Optional: defaults to requirements.txt
dependencies: "numpy scipy" # Optional: inline array of dependencies
mode: "install" # Optional: defaults to installOutputs:
env-zip-path: The full path of the zipped environment
Create beautiful workflow summaries with ease, supporting variable substitution, conditional sections, and pre-defined templates.
uses: melMass/actions@summary
with:
content: |
# 🚀 Deployment Summary
## 📦 Build Information
| Property | Value |
| --- | --- |
| 🔄 Repository | ${repository} |
| 🌿 Branch | ${branch} |
✅ Deployment completed successfully!
variables: '{"repository": "${{ github.repository }}", "branch": "${{ github.ref_name }}"}'An opinionated action for running Nushell scripts with built-in toolkit functions.
uses: melMass/actions@nukit
with:
script: |
let data = {
version: "1.0.0",
status: "success"
}
$data | to-github --output # Outputs to GITHUB_OUTPUT
skip_modules: "false" # Optional: defaults to false
nu-version: "*" # Optional: defaults to latest stableAutomatically syncs a forked repository with its upstream repository and manages the pull request process.
How it works:
- Syncs your fork with the upstream repository using GitHub's
mergeUpstreamAPI - If a PR already exists for the branch, adds a comment with update information
- If no PR exists, creates a new PR to track the changes
Perfect for:
- Maintaining forks of actively developed repositories
- Keeping your fork in sync with the original repository
- Automating the tedious process of syncing forks
uses: melMass/actions@sync-fork
with:
repo-token: ${{ secrets.GITHUB_TOKEN }} # Required: GitHub token with repo access
feature-branch: "main" # Required: branch in your fork to update
upstream-branch: "main" # Required: upstream branch to sync fromExample workflow (scheduled sync):
name: Sync Fork with Upstream
on:
schedule:
- cron: '0 0 * * *' # Runs daily at midnight
workflow_dispatch: # Allows manual triggering
jobs:
sync:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Sync fork with upstream
uses: melMass/actions@sync-fork
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
feature-branch: "main"
upstream-branch: "main"Frees up disk space on GitHub runners by removing unnecessary packages and directories. Perfect for workflows that require additional disk space, such as Docker image builds.
uses: melMass/actions@free-space
with:
remove-dotnet: 'true' # Optional: defaults to true
remove-llvm: 'true' # Optional: defaults to true
remove-php: 'true' # Optional: defaults to true
custom-packages: 'mono-devel libgl1-mesa-dri' # Optional
custom-directories: '/opt/hostedtoolcache/CodeQL' # OptionalOutputs:
space-freed-kb: Disk space freed in KBspace-freed-mb: Disk space freed in MBspace-freed-gb: Disk space freed in GB (with 2 decimal places)initial-space: Initial available disk spacefinal-space: Final available disk space
Deploys a folder to IPFS and returns the CID.
uses: melMass/actions@ipfs
with:
path: "build" # Required: folder to upload, defaults to "build"Outputs:
cid: The CID of the uploaded artifact