Synchronize common repo files across `reactive-python`

Open
#527 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the existing reactive-python repositories and the common files named in the issue: pre-commit-config.yaml, license, code of conduct, contributing, .vscode, and .github. Read the repo-file-sync-action documentation and compare it with the Jazzband setup; done means the shared configurations are synchronized automatically across the relevant repositories.

Written by the indexing model from the issue text.

Description

priority-3-low type-governance
Current Situation

Currently, our repos get basic configuration files out of sync from each other.

Proposed Changes

Synchronize common files (pre-commit-config.yaml, license, code of conduct, contributing, .vscode, .github) via GH actions.

Implementation Details

I recommend using the repo-file-sync GitHub action to automate standardized configurations across reactive-python repos.

That's what we use at Jazzband alongside our template repository.

Dominant language
Python
Stars
8.1k
Forks
332
PR merge metrics
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 reactive-python/reactpy

All issues in reactive-python/reactpy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.