Add Python CI workflow and restrict C/C++ workflow to prevent cross-triggering

[Copilot]

The C/C++ workflow unconditionally ran ./configure on all commits, failing when only Python files changed (configure script doesn't exist). This blocked Python-only PRs.

Changes

• Added .github/workflows/python-package.yml

  • Triggers only on trinity_wallet_py/** changes
  • Runs pytest with dependency caching

• Updated .github/workflows/c-cpp.yml

  • Path filter: src/**, Makefile, trinity-qt.pro, contrib/**, doc/**
  • Guard configure execution: skips if ./configure not present

Result

Python and C/C++ changes now trigger only their respective workflows, preventing spurious failures.

Reference: Failing job | Original workflow

Original prompt

Create a pull request that adds a Python-specific GitHub Actions workflow for the Python package trinity_wallet_py and updates the existing C/C++ workflow so it no longer runs for Python-only changes and guards the configure step. Do not modify any other files.

Context and rationale:

• A failing CI job occurred because the C/C++ workflow ran ./configure on a Python-only change and configure did not exist. Reference failing job: https://github.com/Action-Committee/Trinity_py/actions/runs/20143292221/job/57817586867
• The original C/C++ workflow file to reference is .github/workflows/c-cpp.yml at ref a0c716d.
• The repository contains a Python package at trinity_wallet_py with requirements.txt and test_wallet.py which need CI.

Requested changes (apply in a single branch named ci/add-python-workflow-and-guard-cpp):

1. Add new file: .github/workflows/python-package.yml

Add this exact YAML content (verbatim):

name: Python package CI

on:
push:
branches: [ "master" ]
paths:
- "trinity_wallet_py/"
pull_request:
branches: [ "master" ]
paths:
- "trinity_wallet_py/"

jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: '3.11'
- name: Cache pip
uses: actions/cache@v4
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('trinity_wallet_py/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
- name: Install dependencies
run: |
python -m pip install --upgrade pip
if [ -f trinity_wallet_py/requirements.txt ]; then
pip install -r trinity_wallet_py/requirements.txt
fi
- name: Run tests
run: |
python -m pip install pytest || true
pytest -q trinity_wallet_py/test_wallet.py

2. Replace existing file: .github/workflows/c-cpp.yml

Replace with this exact YAML content (verbatim). This update adds path filters to only trigger on C/C++-related changes and adds a guard around the configure invocation so it won't fail if configure is missing.

name: C/C++ CI

on:
push:
branches: [ "master" ]
paths:
- 'src/'
- 'Makefile'
- 'trinity-qt.pro'
- 'contrib/'
- 'doc/'
- '.github/workflows/c-cpp.yml'
pull_request:
branches: [ "master" ]
paths:
- 'src/'
- 'Makefile'
- 'trinity-qt.pro'
- 'contrib/'
- 'doc/'
- '.github/workflows/c-cpp.yml'

jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: configure
run: |
if [ -x ./configure ]; then
./configure
else
echo "No configure script found; skipping configure step."
fi
- name: make
run: make
- name: make check
run: make check
- name: make distcheck
run: make distcheck

Branch and PR metadata:

• Branch name: ci/add-python-workflow-and-guard-cpp
• Commit message: ci: add Python CI and restrict C/C++ workflow triggers
• PR title: ci: add Python CI workflow for trinity_wallet_py and restrict C/C++ workflow
• PR body: Add a Python-specific CI workflow for trinity_wallet_py and restrict the existing C/C++ workflow so it only runs for C/C++-related changes. This prevents the C/C++ workflow from running (and failing) on Python-only changes. References failing job: https://github.com/Action-Committee/Trinity_py/actions/runs/20143292221/job/57817586867 and the original C/C++ workflow file at ref a0c716d: https://github.com/Action-Committee/Trinity_py/blob/a0c716da4774aa93b1a28705d662bfa6a7ebabe3/.github/workflows/c-cpp.yml
• Merge strategy: merge commit, delete branch after merge.

Sanity and wellness checks to perform before merging:

• Confirm both workflow files are valid YAML and syntactically correct.
• Run a quick lint: ensure no tabs, indentation is spaces.
• Ensure python-package.yml references trinity_wallet_py/requirements.txt and trinity_wallet_py/test_wallet.py which exist in the repo.
• Ensure c-cpp.yml path filters include the main C/C++ build files (Makefile, src/, trinity-qt.pro).

Access and ping checks:

• Verify repository owner is Action-Committee and repo is Trinity_py.
• Confirm that the authenticated bot/token has push and PR merge rights on Action-Committee/Trinity_py.
• Ping the GitHub API to ensure repository is reachable and accept the push/PR operations.

Do NOT modify any other files. After creating the PR, wait for the workflows and checks to complete, then merge the PR if checks pass and delete the branch.

This pull request was created as a result of the following prompt from Copilot chat.

Create a pull request that adds a Python-specific GitHub Actions workflow for the Python package trinity_wallet_py and updates the existing C/C++ workflow so it no longer runs for Python-only changes and guards the configure step. Do not modify any other files.

Context and rationale:

• A failing CI job occurred because the C/C++ workflow ran ./configure on a Python-only change and configure did not exist. Reference failing job: https://github.com/Action-Committee/Trinity_py/actions/runs/20143292221/job/57817586867
• The original C/C++ workflow file to reference is .github/workflows/c-cpp.yml at ref a0c716d.
• The repository contains a Python package at trinity_wallet_py with requirements.txt and test_wallet.py which need CI.

Requested changes (apply in a single branch named ci/add-python-workflow-and-guard-cpp):

1. Add new file: .github/workflows/python-package.yml

Add this exact YAML content (verbatim):

name: Python package CI

on:
push:
branches: [ "master" ]
paths:
- "trinity_wallet_py/"
pull_request:
branches: [ "master" ]
paths:
- "trinity_wallet_py/"

jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: '3.11'
- name: Cache pip
uses: actions/cache@v4
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('trinity_wallet_py/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
- name: Install dependencies
run: |
python -m pip install --upgrade pip
if [ -f trinity_wallet_py/requirements.txt ]; then
pip install -r trinity_wallet_py/requirements.txt
fi
- name: Run tests
run: |
python -m pip install pytest || true
pytest -q trinity_wallet_py/test_wallet.py

2. Replace existing file: .github/workflows/c-cpp.yml

Replace with this exact YAML content (verbatim). This update adds path filters to only trigger on C/C++-related changes and adds a guard around the configure invocation so it won't fail if configure is missing.

name: C/C++ CI

on:
push:
branches: [ "master" ]
paths:
- 'src/'
- 'Makefile'
- 'trinity-qt.pro'
- 'contrib/'
- 'doc/'
- '.github/workflows/c-cpp.yml'
pull_request:
branches: [ "master" ]
paths:
- 'src/'
- 'Makefile'
- 'trinity-qt.pro'
- 'contrib/'
- 'doc/'
- '.github/workflows/c-cpp.yml'

jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: configure
run: |
if [ -x ./configure ]; then
./configure
else
echo "No configure script found; skipping configure step."
fi
- name: make
run: make
- name: make check
run: make check
- name: make distcheck
run: make distcheck

Branch and PR metadata:

• Branch name: ci/add-python-workflow-and-guard-cpp
• Commit message: ci: add Python CI and restrict C/C++ workflow triggers
• PR title: ci: add Python CI workflow for trinity_wallet_py and restrict C/C++ workflow
• PR body: Add a Python-specific CI workflow for trinity_wallet_py and restrict the existing C/C++ workflow so it only runs for C/C++-related changes. This prevents the C/C++ workflow from running (and failing) on Python-only changes. References failing job: https://github.com/Action-Committee/Trinity_py/actions/runs/20143292221/job/57817586867 and the original C/C++ workflow file at ref a0c716d: https://github.com/Action-Committee/Trinity_py/blob/a0c716da4774aa93b1a28705d662bfa6a7ebabe3/.github/workflows/c-cpp.yml
• Merge strategy: merge commit, delete branch after merge.

Sanity and wellness checks to perform before merging:

• Confirm both workflow files are valid YAML and syntactically correct.
• Run a quick lint: ensure no tabs, indentation is spaces.
• Ensure python-package.yml references trinity_wallet_py/requirements.txt and trinity_wallet_py/test_wallet.py which exist in the repo.
• Ensure c-cpp.yml path filters include the main C/C++ build files (Makefile, src/, trinity-qt.pro).

Access and ping checks:

• Verify repository owner is Action-Committee and repo is Trinity_py.
• Confirm that the authenticated bot/token has push and PR merge rights on Action-Committee/Trinity_py.
• Ping the GitHub API to ensure repository is reachable and accept the push/PR operations.

Do NOT modify any other files. After creating the PR, wait for the workflows and checks to complete, then merge the PR if checks pass and delete the branch.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.