Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

I have built an Action that can help to automatically build a Python project with PyStand.

Open
  • Is something wrong?
#105 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, python
Domain
build-system, devops

Research direction

Start with the linked action repository, BHznJNs/pystand-build, and the workflow example in this issue. The payload does not identify a PyStand file, test, requested change, or acceptance criteria, so the intended project-side work and definition of done remain unclear.

Written by the indexing model from the issue text.

Description

Here is the action repo link:
https://github.com/BHznJNs/pystand-build

This is the use example which is modified from my own repo:

jobs:
  build:
    runs-on: windows-latest
      - name: Checkout
        uses: actions/checkout@v4

      - name: Build Python Application Standalone Package
        id: pystand-build
        uses: BHznJNs/pystand-build@release-2
        with:
          application-name: "YourApplicationName"
          python-version: "3.11.9"
          requirements-path: "backend/requirements.txt"
          included-files: |
            backend/ # this is the python source directory
            # there can be other assets files or directories here

      - name: Create Zip Archive
        shell: bash
        run: |
          build_path="${{ steps.pystand-build.outputs.build-directory }}"
          (cd "$build_path" && 7z a -tzip "$RUNNER_TEMP/GibberishSubtitle.zip" .)

      # upload package with `${{ runner.temp }}/GibberishSubtitle.zip`
Dominant language
C++
Stars
1.2k
Forks
146
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from skywind3000/PyStand

All issues in skywind3000/PyStand

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.