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

Add CI to check that code has been formatted with pyink formatter.

Open
#71 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
ci-cd, tooling

Research direction

Start by inspecting the repository's existing CI configuration and Python formatting setup, then review the linked pyink project to understand the requested formatter check. Done means CI automatically detects code that is not formatted with the requested pyink configuration, including its two-space indentation.

Written by the indexing model from the issue text.

Description

          One other thing I'll note is that I've been formatting code in Xarray-Beam with the (Google internal) version of the "pyink" formatter, using 2 space indentation: https://github.com/google/pyink

It would be nice if you could apply that manually to this change -- ideally we would add some sort of automatic formatter checker.

Originally posted by @shoyer in https://github.com/google/xarray-beam/issues/69#issuecomment-1380907751

Dominant language
Python
Stars
170
Forks
15
Avg merge
18h 27m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

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 google/xarray-beam

All issues in google/xarray-beam

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.