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

Inhance the CI publishing section

Open
#57 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
ci-cd, release

Research direction

No files or tests are named; start by locating the repository's CI configuration, version source, test commands, and existing PyPI publishing setup. Done means pushes and non-master pull requests run the test suites, while merges into master alone bump the version and publish to PyPI.

Written by the indexing model from the issue text.

Description

@Naramsim Hi there.
Once you guys figure out the Pypi bureaucracy,
I'd like to propose changing the CI and automating the publishing process.

The CI will be split to 2 scenarios:

  1. Push. Any push to any branch will trigger all the testing suites. Same goes for non-master PRs.
  2. when a PR gets merged into master and only into master an automatic process will bump the version and execute the Pypi publish command.

Let me know if this sounds, and if it is, when we can start work on to :)

Dominant language
Python
Stars
361
Forks
58
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 PokeAPI/pokebase

All issues in PokeAPI/pokebase

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.